Mulakan

Cari dalam skrip untuk "THE SCRIPT"

CVD - Cumulative Volume Delta (Chart)█   OVERVIEW This indicator displays cumulative ​volume delta (​CVD) as an on-chart oscillator. It uses intrabar analysis to obtain more precise ​volume delta information compared to methods that only use the chart's timeframe. The core concepts in this script come from our first ​ CVD indicator , which displays CVD​ values as plot candles in a separate indicator pane. In this script, CV​D values are scaled according to price ranges and represented on the main chart pane. █   CONCEPTS Bar polarity Bar polarity refers to the position of the close price relative to the open price. In other words, bar polarity is the direction of price change. Intrabars Intrabars are chart bars at a lower timeframe than the chart's. Each 1H chart bar of a 24x7 market will, for example, usually contain 60 bars at the lower timeframe of 1min, provided there was market activity during each minute of the hour. Mining information from intrabars can be useful in that it offers traders visibility on the activity inside a chart bar. Lower timeframes (LTFs) A lower timeframe is a timeframe that is smaller than the chart's timeframe. This script utilizes a LTF to analyze intrabars, or price changes within a chart bar. The lower the ​LTF, the more intrabars are analyzed, but the less chart bars can display information due to the limited number of intrabars that can be analyzed. Volume delta Volume delta is a measure that separates ​volume​ into "up" and "down" parts, then takes the difference to estimate the net demand for the asset. This approach gives traders a more detailed insight when analyzing volume​ and market sentiment. There are several methods for determining whether an asset's volume​ belongs in the "up" or "down" category. Some indicators, such as On Balance Volume​ and the Klinger Oscillator , use the change in price between bars to assign ​volume​ values to the appropriate category. Others, such as Chaikin Money Flow , make assumptions based on open, high, low, and close prices. The most accurate method involves using tick data to determine whether each transaction occurred at the bid or ask price and assigning the ​volume​ value to the appropriate category accordingly. However, this method requires a large amount of data on historical bars, which can limit the historical depth of charts and the number of symbols for which tick data is available. In the context where historical tick data is not yet available on TradingView, intrabar analysis is the most precise technique to calculate ​volume delta on historical bars on our charts. This indicator uses intrabar analysis to achieve a compromise between simplicity and accuracy in calculating ​volume delta on historical bars. Our Volume Profile indicators use it as well. Other ​volume delta indicators in our Community Scripts , such as the Realtime 5D Profile , use real-time chart updates to achieve more precise ​volume delta calculations. However, these indicators aren't suitable for analyzing historical bars since they only work for real-time analysis. This is the logic we use to assign intrabar ​volume to the "up" or "down" category:  • If the intrabar's open and close values are different, their relative position is used.  • If the intrabar's open and close values are the same, the difference between the intrabar's close and the previous intrabar's close is used.  • As a last resort, when there is no movement during an intrabar and it closes at the same price as the previous intrabar, the last known polarity is used. Once all intrabars comprising a chart bar are analyzed, we calculate the net difference between "up" and "down" intrabar volume​ to produce the volume​ delta for the chart bar. █   FEATURES CVD resets The "cumulative" part of the indicator's name stems from the fact that calculations accumulate during a period of time. By periodically resetting the volume​ delta accumulation, we can analyze the progression of ​volume delta across manageable chunks, which is often more useful than looking at ​volume delta accumulated from the beginning of a chart's history. You can configure the reset period using the "CVD Resets" input, which offers the following selections:  • None : Calculations do not reset.  • On a fixed higher timeframe : Calculations reset on the higher timeframe you select in the "Fixed higher timeframe" field.  • At a fixed time that you specify.  • At the beginning of the regular session .  • On trend changes : Calculations reset on the direction change of either the Aroon indicator, Parabolic SAR , or Supertrend .  • On a stepped higher timeframe : Calculations reset on a higher timeframe automatically stepped using the chart's timeframe and following these rules: Chart TF ​HTF < 1min 1H < 3H 1D <= 12H 1W < 1W 1M >= 1W 1Y Specifying intrabar precision Ten options are included in the script to control the number of intrabars used per chart bar for calculations. The greater the number of intrabars per chart bar, the fewer chart bars can be analyzed. The first five options allow users to specify the approximate amount of chart bars to be covered:  • Least Precise (Most chart bars) : Covers all chart bars by dividing the current timeframe by four.   This ensures the highest level of intrabar precision while achieving complete coverage for the dataset.  • Less Precise (Some chart bars) & More Precise (Less chart bars) : These options calculate a stepped ​LTF in relation to the current chart's timeframe.  • Very precise (2min intrabars) : Uses the second highest quantity of intrabars possible with the 2min ​LTF.  • Most precise (1min intrabars) : Uses the maximum quantity of intrabars possible with the 1min ​LTF. The stepped lower timeframe for "Less Precise" and "More Precise" options is calculated from the current chart's timeframe as follows: Chart Timeframe Lower Timeframe Less Precise More Precise < 1hr 1min 1min < 1D 15min 1min < 1W ​2hr​ 30min > 1W 1D 60min The last five options allow users to specify an approximate fixed number of intrabars to analyze per chart bar. The available choices are 12, 24, 50, 100, and 250. The script will calculate the LTF​ which most closely approximates the specified number of intrabars per chart bar. Keep in mind that due to factors such as the length of a ticker's sessions and rounding of the LTF​, it is not always possible to produce the exact number specified. However, the script will do its best to get as close to the value as possible. As there is a limit to the number of intrabars that can be analyzed by a script, a tradeoff occurs between the number of intrabars analyzed per chart bar and the chart bars for which calculations are possible. Display This script displays raw or cumulative volume​ delta values on the chart as either line or histogram oscillator zones scaled according to the price chart, allowing traders to visualize volume​ activity on each bar or cumulatively over time. The indicator's background shows where CVD​ resets occur, demarcating the beginning of new zones. The vertical axis of each oscillator zone is scaled relative to the one with the highest price range, and the oscillator values are scaled relative to the highest volume​ delta. A vertical offset is applied to each oscillator zone so that the highest oscillator value aligns with the lowest price. This method ensures an accurate, intuitive visual comparison of volume​ activity within zones, as the scale is consistent across the chart, and oscillator values sit below prices. The vertical scale of oscillator zones can be adjusted using the "Zone Height" input in the script settings. This script displays labels at the highest and lowest oscillator values in each zone, which can be enabled using the "Hi/Lo Labels" input in the "Visuals" section of the script settings. Additionally, the oscillator's value on a chart bar is displayed as a tooltip when a user hovers over the bar, which can be enabled using the "Value Tooltips" input. Divergences occur when the polarity of ​volume delta does not match that of the chart bar. The script displays divergences as bar colors and background colors that can be enabled using the "Color bars on divergences" and "Color background on divergences" inputs. An information box in the lower-left corner of the indicator displays the HTF used for resets, the ​LTF used for intrabars, the average quantity of intrabars per chart bar, and the number of chart bars for which there is LTF data. This is enabled using the "Show information box" input in the "Visuals" section of the script settings. FOR Pine Script™ CODERS  • This script utilizes `ltf()` and `ltfStats()` from the lower_tf library.   The `ltf()` function determines the appropriate lower timeframe from the selected calculation mode and chart timeframe, and returns it in a format that can be used with request.security_lower_tf() .   The `ltfStats()` function, on the other hand, is used to compute and display statistical information about the lower timeframe in an information box.  • The script utilizes display.data_window and display.status_line to restrict the display of certain plots.   These new built-ins allow coders to fine-tune where a script’s plot values are displayed.  • The newly added session.isfirstbar_regular built-in allows for resetting the ​CVD segments at the start of the regular session.  • The VisibleChart library developed by our resident PineCoders team leverages the chart.left_visible_bar_time and chart.right_visible_bar_time variables to optimize the performance of this script.   These variables identify the opening time of the leftmost and rightmost visible bars on the chart, allowing the script to recalculate and draw objects only within the range of visible bars as the user scrolls.   This functionality also enables the scaling of the oscillator zones.   These variables are just a couple of the many new built-ins available in the chart.* namespace.   For more information, check out this blog post or look them up by typing "chart." in the Pine Script™ Reference Manual .  • Our ta library has undergone significant updates recently, including the incorporation of the `aroon()` indicator used as a method for resetting ​CVD segments within this script.   Revisit the library to see more of the newly added content! Look first. Then leap.
Penunjuk Pine Script®
oleh TradingView
57
Delta Volume Columns Pro [LucF]█  OVERVIEW This indicator displays volume​​ delta information calculated with intrabar inspection on historical bars, and feed updates when running in realtime. It is designed to run in a pane and can display either stacked buy/sell volume​ columns or a signal line which can be calculated and displayed in many different ways. Five different models are offered to reveal different characteristics of the calculated volume​ delta information. Many options are offered to visualize the calculations, giving you much leeway in morphing the indicator's visuals to suit your needs. If you value delta volume​ information, I hope you will find the time required to master Delta Volume​ Columns Pro well worth the investment. I am confident that if you combine a proper understanding of the indicator's information with an intimate knowledge of the volume​ idiosyncrasies on the markets you trade, you can extract useful market intelligence using this tool. █  WARNINGS 1. The indicator only works on markets where volume​ information is available,   Please validate that your symbol's feed carries volume​ information before asking me why the indicator doesn't plot values. 2. When you refresh your chart or re-execute the script on the chart, the indicator will repaint because elapsed realtime bars will then recalculate as historical bars. 3. Because the indicator uses different modes of calculation on historical and realtime bars, it's critical that you understand the differences between them. Details are provided further down. 4. Calculations using intrabar inspection on historical bars can only be done from some chart timeframes. See further down for a list of supported timeframes.   If the chart's timeframe is not supported, no historical volume​ delta will display. █  CONCEPTS Chart bars Three different types of bars are used in charts:  1. Historical bars are bars that have already closed when the script executes on them.  2. The realtime bar is the current, incomplete bar where a script is running on an open market. There is only one active realtime bar on your chart at any given time.    The realtime bar is where alerts trigger.  3. Elapsed realtime bars are bars that were calculated when they were realtime bars but have since closed.    When a script re-executes on a chart because the browser tab is refreshed or some of its inputs are changed, elapsed realtime bars are recalculated as historical bars. Why does this indicator use two modes of calculation? Historical bars on TradingView charts contain OHLCV data only, which is insufficient to calculate volume​ delta on them with any level of precision. To mine more detailed information from those bars we look at intrabars , i.e., bars from a smaller timeframe (we call it the intrabar timeframe ) that are contained in one chart bar. If your chart Is running at 1D on a 24x7 market for example, most 1D chart bars will contain 24 underlying 1H bars in their dilation. On historical bars, this indicator looks at those intrabars to amass volume​ delta information. If the intrabar is up, its volume​ goes in the Buy bin, and inversely for the Sell bin. When price does not move on an intrabar, the polarity of the last known movement is used to determine in which bin its volume​ goes. In realtime, we have access to price and volume​ change for each update of the chart. Because a 1D chart bar can be updated tens of thousands of times during the day, volume​ delta calculations on those updates is much more precise. This precision, however, comes at a price:  — The script must be running on the chart for it to keep calculating in realtime.  — If you refresh your chart you will lose all accumulated realtime calculations on elapsed realtime bars, and the realtime bar.   Elapsed realtime bars will recalculate as historical bars, i.e., using intrabar inspection, and the realtime bar's calculations will reset.   When the script recalculates elapsed realtime bars as historical bars, the values on those bars will change, which means the script repaints in those conditions.  — When the indicator first calculates on a chart containing an incomplete realtime bar, it will count ALL the existing volume​ on the bar as Buy or Sell volume​,   depending on the polarity of the bar at that point. This will skew calculations for that first bar. Scripts have no access to the history of a realtime bar's previous updates,   and intrabar inspection cannot be used on realtime bars, so this is the only to go about this.  — Even if alerts only trigger upon confirmation of their conditions after the realtime bar closes, they are repainting alerts   because they would perhaps not have calculated the same way using intrabar inspection.  — On markets like stocks that often have different EOD​ and intraday feeds and volume​ information,   the volume's scale may not be the same for the realtime bar if your chart is at 1D, for example,   and the indicator is using an intraday timeframe to calculate on historical bars.  — Any chart timeframe can be used in realtime mode, but plots that include moving averages in their calculations may require many elapsed realtime bars before they can calculate.   You might prefer drastically reducing the periods of the moving averages, or using the volume​ columns mode, which displays instant values, instead of the line. Volume Delta Balances This indicator uses a variety of methods to evaluate five volume​ delta balances and derive other values from those balances. The five balances are: 1 — On Bar Balance : This is the only balance using instant values; it is simply the subtraction of the Sell volume​ from the Buy volume​ on the bar. 2 — Average Balance : Calculates a distinct EMA for both the Buy and Sell volumes, and subtracts the Sell EMA from the Buy EMA. 3 — Momentum Balance : Starts by calculating, separately for both Buy and Sell volumes, the difference between the same EMAs used in "Average Balance" and   an SMA of double the period used for the "Average Balance" EMAs. The difference for the Sell side is subtracted from the difference for the Buy side,   and an RSI of that value is calculated and brought over the −50/+50 scale. 4 — Relative Balance : The reference values used in the calculation are the Buy and Sell EMAs used in the "Average Balance".   From those, we calculate two intermediate values using how much the instant Buy and Sell volumes on the bar exceed their respective EMA — but with a twist.   If the bar's Buy volume​ does not exceed the EMA of Buy volume​, a zero value is used. The same goes for the Sell volume​ with the EMA of Sell volume​.   Once we have our two intermediate values for the Buy and Sell volumes exceeding their respective MA, we subtract them. The final "Relative Balance" value is an ALMA of that subtraction.   The rationale behind using zero values when the bar's Buy/Sell volume​ does not exceed its EMA is to only take into account the more significant volume​.   If both instant volume​ values exceed their MA, then the difference between the two is the signal's value.   The signal is called "relative" because the intermediate values are the difference between the instant Buy/Sell volumes and their respective MA.   This balance flatlines when the bar's Buy/Sell volumes do not exceed their EMAs, which makes it useful to spot areas where trader interest dwindles, such as consolidations.   The smaller the period of the final value's ALMA, the more easily you will see the balance flatline. These flat zones should be considered no-trade zones. 5 — Percent Balance : This balance is the ALMA of the ratio of the "On Bar Balance" value, i.e., the volume​ delta balance on the bar (which can be positive or negative),   over the total volume for that bar. From the balances and marker conditions, two more values are calculated: 1 — Marker Bias : It sums the up/down (+1/‒1) occurrences of the markers 1 to 4 over a period you define, so it ranges from −4 to +4, times the period.   Its calculation will depend on the modes used to calculate markers 3 and 4. 2 — Combined Balances : This is the sum of the bull/bear (+1/−1) states of each of the five balances, so it ranges from −5 to +5. █  FEATURES The indicator has two main modes of operation: Columns and Line . Columns • In Columns mode you can display stacked Buy/Sell volume​ columns. • The buy section always appears above the centerline, the sell section below. • The top and bottom sections can be colored independently using eight different methods. • The EMAs of the Buy/Sell values can be displayed (these are the same EMAs used to calculate the "Average Balance"). Line • Displays one of seven signals: the five balances or one of two complementary values, i.e., the "Marker Bias" or the "Combined Balances". • You can color the line and its fill using independent calculation modes to pack more information in the display.  You can thus appraise the state of 3 different values using the line itself, its color and the color of its fill. • A "Divergence Levels" feature will use the line to automatically draw expanding levels on divergence events. Default settings Using the indicator's default settings, this is the information displayed: • The line is calculated on the "Average Balance". • The line's color is determined by the bull/bear state of the "Percent Balance". • The line's fill gradient is determined by the advances/declines of the "Momentum Balance". • The orange divergence dots are calculated using discrepancies between the polarity of the "On Bar Balance" and the chart's bar. • The divergence levels are determined using the line's level when a divergence occurs. • The background's fill gradient is calculated on advances/declines of the "Marker Bias". • The chart bars are colored using advances/declines of the "Relative Balance". Divergences are shown in orange. • The intrabar timeframe is automatically determined from the chart's timeframe so that a minimum of 50 intrabars are used to calculate volume​ delta on historical bars. Alerts The configuration of the marker conditions explained further is what determines the conditions that will trigger alerts created from this script. Note that simply selecting the display of markers does not create alerts. To create an alert on this script, you must use ALT-A from the chart. You can create multiple alerts triggering on different conditions from this same script; simply configure the markers so they define the trigger conditions for each alert before creating the alert. The configuration of the script's inputs is saved with the alert, so from then on you can change them without affecting the alert. Alert messages will mention the marker(s) that triggered the specific alert event. Keep in mind, when creating alerts on small chart timeframes, that discrepancies between alert triggers and markers displayed on your chart are to be expected. This is because the alert and your chart are running two distinct instances of the indicator on different servers and different feeds. Also keep in mind that while alerts only trigger on confirmed conditions, they are calculated using realtime calculation mode, which entails that if you refresh your chart and elapsed realtime bars recalculate as historical bars using intrabar inspection, markers will not appear in the same places they appeared in realtime. So it's important to understand that even though the alert conditions are confirmed when they trigger, these alerts will repaint. Let's go through the sections of the script's inputs. Columns The size of the Buy/Sell columns always represents their respective importance on the bar, but the coloring mode for tops and bottoms is independent. The default setup uses a standard coloring mode where the Buy/Sell columns are always in the bull/bear color with a higher intensity for the winning side. Seven other coloring modes allow you to pack more information in the columns. When choosing to color the top columns using a bull/bear gradient on "Average Balance", for example, you will have bull/bear colored tops. In order for the color of the bottom columns to continue to show the instant bar balance, you can then choose the "On Bar Balance — Dual Solid Colors" coloring mode to make those bars the color of the winning side for that bar. You can display the averages of the Buy and Sell columns. If you do, its coloring is controlled through the "Line" and "Line fill" sections below. Line and Line fill You can select the calculation mode and the thickness of the line, and independent calculations to determine the line's color and fill. Zero Line The zero line can display dots when all five balances are bull/bear. Divergences You first select the detection mode. Divergences occur whenever the up/down direction of the signal does not match the up/down polarity of the bar. Divergences are used in three components of the indicator's visuals: the orange dot, colored chart bars, and to calculate the divergence levels on the line. The divergence levels are dynamic levels that automatically build from the line's values on divergence events. On consecutive divergences, the levels will expand, creating a channel. This implementation of the divergence levels corresponds to my view that divergences indicate anomalies, hesitations, points of uncertainty if you will. It precludes any attempt to identify a directional bias to divergences. Accordingly, the levels merely take note of divergence events and mark those points in time with levels. Traders then have a reference point from which they can evaluate further movement. The bull/bear/neutral colors used to plot the levels are also congruent with this view in that they are determined by the line's position relative to the levels, which is how I think divergences can be put to the most effective use. One of the coloring modes for the line's fill uses advances/declines in the line after divergence events. Background The background can show a bull/bear gradient on six different calculations. As with other gradients, you can adjust its brightness to make its importance proportional to how you use it in your analysis. Chart bars Chart bars can be colored using seven different methods. You have the option of emptying the body of bars where volume​ does not increase, as does my TLD indicator, and you can choose whether you want to show divergences. Intrabar Timeframe This is the intrabar timeframe that will be used to calculate volume​ delta using intrabar inspection on historical bars. You can choose between four modes. The three "Auto-steps" modes calculate, from the chart's timeframe, the intrabar timeframe where the said number of intrabars will make up the dilation of chart bars. Adjustments are made for non-24x7 markets. "Fixed" mode allows you to select the intrabar timeframe you want. Checking the "Show TF" box will display in the lower-right corner the intrabar timeframe used at any given moment. The proper selection of the intrabar timeframe is important. It must achieve maximal granularity to produce precise results while not unduly slowing down calculations, or worse, causing runtime errors. Note that historical depth will vary with the intrabar timeframe. The smaller the timeframe, the shallower historical plots you will be. Markers Markers appear when the required condition has been confirmed on a closed bar. The configuration of the markers when you create an alert is what determines when the alert will trigger. Five markers are available: • Balances Agreement : All five balances are either bullish​ or bearish​. • Double Bumps : A double bump is two consecutive up/down bars with +/‒ volume​​ delta, and rising Buy/Sell volume​ above its average. • Divergence confirmations : A divergence is confirmed up/down when the chosen balance is up/down on the previous bar when that bar was down/up, and this bar is up/down. • Balance Shifts : These are bull/bear transitions of the selected signal. • Marker Bias Shifts : Marker bias shifts occur when it crosses into bull/bear territory. Periods Allows control over the periods of the different moving averages used to calculate the balances. Volume​ Discrepancies Stock exchanges do not report the same volume​ for intraday and daily (or higher) resolutions. Other variations in how volume​ information is reported can also occur in other markets, namely Forex, where volume​ irregularities can even occur between different intraday timeframes. This will cause discrepancies between the total volume​ on the bar at the chart's timeframe, and the total volume​​ calculated by adding the volume​​ of the intrabars in that bar's dilation. This does not necessarily invalidate the volume​​ delta information calculated from intrabars, but it tells us that we are using partial volume​ data. A mechanism to detect chart vs intrabar timeframe volume​​ discrepancies is provided. It allows you to define a threshold percentage above which the background will indicate a difference has been detected. Other Settings You can control here the display of the gray dot reminder on realtime bars, and the display of error messages if you are using a chart timeframe that is not greater than the fixed intrabar timeframe, when you use that mode. Disabling the message can be useful if you only use realtime mode at chart timeframes that do not support intrabar inspection. █  RAMBLINGS On Volume​ Delta Volume​ is arguably the best complement to interpret price action, and I consider volume​ delta to be the most effective way of processing volume​ information. In periods of low-volatility price consolidations, volume​ will typically also be lower than normal, but slight imbalances in the trend of the buy/sell volume​ balance can sometimes help put early odds on the direction of the break from consolidation. Additionally, the progression of the volume​ imbalance can help determine the proximity of the breakout. I also find volume​ delta and the number of divergences very useful to evaluate the strength of trends. In trends, I am looking for "slow and steady", i.e., relatively low volatility​ and pauses where price action doesn't look like world affairs are being reassessed. In my personal mythology, this type of trend is often more resilient than high-volatility breakouts, especially when volume​ balance confirms the general agreement of traders signaled by the low-volatility usually accompanying this type of trend. The volume​ action on pauses will often help me decide between aggressively taking profits, tightening a stop or going for a longer-term movement. As for reversals, they generally occur in high-volatility areas where entering trades is more expensive and riskier. While the identification of counter-trend reversals fascinates many traders to no end, they represent poor opportunities in my view. Volume​ imbalances often precede reversals, but I prefer to use volume​ delta information to identify the areas following reversals where I can confirm them and make relatively low-cost entries with better odds. On "Buy/Sell" Volume Buying or selling volume​ are misnomers, as every unit of volume​ transacted is both bought and sold by two different traders. While this does not keep me from using the terms, there is no such thing as “buy only” or “sell only” volume​. Trader lingo is riddled with peculiarities. Divergences The divergence detection method used here relies on a difference between the direction of a signal and the polarity (up/down) of a chart bar. When using the default "On Bar Balance" to detect divergences, however, only the bar's volume​ delta is used. You may wonder how there can be divergences between buying/selling volume​ information and price movement on one bar. This will sometimes be due to the calculation's shortcomings, but divergences may also occur in instances where because of order book structure, it takes less volume​ to increase the price of an asset than it takes to decrease it. As usual, divergences are points of interest because they reveal imbalances, which may or may not become turning points. To your pattern-hungry brain, the divergences displayed by this indicator will — as they do on other indicators — appear to often indicate turnarounds. My opinion is that reality is generally quite sobering and I have no reliable information that would tend to prove otherwise. Exercise caution when using them. Consequently, I do not share the overwhelming enthusiasm of traders in identifying bullish​/bearish​ divergences. For me, the best course of action when a divergence occurs is to wait and see what happens from there. That is the rationale underlying how my divergence levels work; they take note of a signal's level when a divergence occurs, and it's the signal's behavior from that point on that determines if the post-divergence action is bullish​/bearish​. Superfluity In "The Bed of Procrustes", Nassim Nicholas Taleb writes: To bankrupt a fool, give him information . This indicator can display lots of information. While learning to use a new indicator inevitably requires an adaptation period where we put it through its paces and try out all its options, once you have become used to it and decide to adopt it, rigorously eliminate the components you don't use and configure the remaining ones so their visual prominence reflects their relative importance in your analysis. I tried to provide flexible options for traders to control this indicator's visuals for that exact reason — not for window dressing. █  LIMITATIONS • This script uses a special characteristic of the `security()` function allowing the inspection of intrabars — which is not officially supported by TradingView.  It has the advantage of permitting a more robust calculation of volume​ delta than other methods on historical bars, but also has its limits. • Intrabar inspection only works on some chart timeframes: 3, 5, 10, 15 and 30 minutes, 1, 2, 3, 4, 6, and 12 hours, 1 day, 1 week and 1 month.  The script’s code can be modified to run on other resolutions. • When the difference between the chart’s timeframe and the intrabar timeframe is too great, runtime errors will occur. The Auto-Steps selection mechanisms should avoid this. • All volume​ is not created equally. Its source, components, quality and reliability will vary considerably with sectors and instruments.  The higher the quality, the more reliably volume​ delta information can be used to guide your decisions.  You should make it your responsibility to understand the volume​ information provided in the data feeds you use. It will help you make the most of volume​ delta. █  NOTES For traders • The Data Window shows key values for the indicator. • While this indicator displays some of the same information calculated in my Delta Volume Columns ,  I have elected to make it a separate publication so that traders continue to have a simpler alternative available to them. Both code bases will continue to evolve separately. • All gradients used in this indicator determine their brightness intensities using advances/declines in the signal—not their relative position in a pre-determined scale. • Volume​ delta being relative, by nature, it is particularly well-suited to Forex markets, as it filters out quite elegantly the cyclical volume​ data characterizing the sector. If you are interested in volume​ delta, consider having a look at my other "Delta Volume" indicators: • Delta Volume Realtime Action displays realtime volume​ delta and tick information on the chart. • Delta Volume Candles builds volume​​ delta candles on the chart. • Delta Volume Columns is a simpler version of this indicator. For coders • I use the `f_c_gradientRelativePro()` from the PineCoders Color Gradient Framework to build my gradients.  This function has the advantage of allowing begin/end colors for both the bull and bear colors. It also allows us to define the number of steps allowed for each gradient.  I use this to modulate the gradients so they perform optimally on the combination of the signal used to calculate advances/declines,  but also the nature of the visual component the gradient applies to. I use fewer steps for choppy signals and when the gradient is used on discrete visual components  such as volume​ columns or chart bars. • I use the PineCoders Coding Conventions for Pine to write my scripts. • I used functions modified from the PineCoders MTF Selection Framework for the selection of timeframes. █  THANKS TO: — The devs from TradingView's Pine and other teams, and the PineCoders who collaborate with them. They are doing amazing work,  and much of what this indicator does could not be done without their recent improvements to Pine. — A guy called Kuan who commented on a Backtest Rookies presentation of their Volume Profile indicator using a `for` loop.  This indicator started from the intrabar inspection technique illustrated in Kuan's snippet. — theheirophant , my partner in the exploration of the sometimes weird abysses of `security()`’s behavior at intrabar timeframes. — midtownsk8rguy , my brilliant companion in mining the depths of Pine graphics.
Penunjuk Pine Script®
oleh LucF
125
Vertical LinesThis script plots vertical lines on charts or indicators. Unfortunately pinescript is lacking a vertical line plotting function. Vertical lines are useful to mark events, such as crossover of levels, indicators signals or as a time marker. After searching the internet for a long time and trying different scripts, this script is the simplest and visually the best. You would think that plotting a vertical line would be relatively easy, it is not! I thank the unknow author for sharing this solution and now I will share it on tradingview to make it readily available to anybody that needs it. RSI crossover signals are used as an example in this script. When the RSI crosses over 70 or below 30, the script plots a red or green vertical line. The script plots a vertical line as a histogram bar. The histogram bar must have a height. Setting the height near infinity like 1e20 will cover all the ranges from top to bottom in most charts, but doesn't work all the time. If the chart range is small in values, the line is not plotted or the chart is visually compressed because the top of the bar is also a data point in the chart. Another solution is to find the highest point in the chart and multiply it by a number from 2 to 10 to set the top of the histogram bar. But this solution doesn't work if the line is drawn in the indicator window. additionally if the chart or indicator includes negative values, a histogram bar with a negative height must be concatenated to the histogram bar with a positive height to cover the positive and negative range. It would seem intuitive to include a vertical plot function since it is very useful and pinescript already has a horizontal line plot function called Hline. But pinescript is becoming less intuitive, and redundant. A case in point is Version 4 variable declaration and naming, it less intuitive and more redundant than previous versions. I beg Tradingview to adopt a more refined scripting language such as Matlab or Python for charting purposes. These languages can be easily ported to other analysis programs for AI or statistical analysis.
Penunjuk Pine Script®
oleh nagihatoum
4
Realtime Delta Volume Action [LucF]█  OVERVIEW This indicator displays on-chart, realtime, delta volume​ and delta ticks information for each bar. It aims to provide traders who trade price action on small timeframes with volume​ and tick information gathered as updates come in the chart's feed. It builds its own candles, which are optimized to display volume​ delta information. It only works in realtime. █  WARNING This script is intended for traders who can already profitably trade discretionary on small timeframes. The high cost in fees and the excitement of trading at small timeframes have ruined many newcomers to trading. While trading at small timeframes can work magic for adrenaline junkies in search of thrills rather than profits, I DO NOT recommend it to most traders. Only seasoned discretionary traders able to factor in the relatively high cost of such a trading practice can ever hope to take money out of markets in that type of environment, and I would venture​ they account for an infinitesimal percentage of traders. If you are a newcomer to trading, AVOID THIS TOOL AT ALL COSTS — unless you are interested in experimenting with the interpretation of volume​ delta combined with price action. No tool currently available on TradingView provides this type of close monitoring of volume​ delta information, but if you are not already trading small timeframes profitably, please do not let yourself become convinced that it is the missing piece you needed. Avoid becoming a sucker who only contributes by providing liquidity to markets. The information calculated by the indicator cannot be saved on charts, nor can it be recalculated from historical bars. If you refresh the chart or restart the script, the accumulated information will be lost. █  FEATURES Key values The script displays the following key values:  • Above the bar: ticks delta​ (DT​), the total ticks​ for the bar, the percentage of total ticks that DT​ represents (DT%)  • Below the bar: volume delta​ (DV​), the total volume​ for the bar, the percentage of total volume​ that DV​ represents (DV%). Candles Candles are composed of four components:  1. A top shaped like this: ┴, and a bottom shaped like this: ┬ (picture a normal Japanese candle without a body outline; the values used are the same).  2. The candle bodies are filled with the bull/bear color representing the polarity of DV​. The intensity of the body's color is determined by the DV% value.    When DV% is 100, the intensity of the fill is brightest. This plays well in interpreting the body colors, as the smaller, less significant DV% values will produce less vivid colors.  3. The bright-colored borders of the candle bodies occur on "strong bars", i.e., bars meeting the criteria selected in the script's inputs, which you can configure.  4. The POC line is a small horizontal line that appears to the left of the candle. It is the volume-weighted average of all price updates during the bar. Calculations This script monitors each realtime update of the chart's feed. It first determines if price has moved up or down since the last update. The polarity of the price change, in turn, determines the polarity of the volume​​ and tick for that specific update. If price does not move between consecutive updates, then the last known polarity is used. Using this method, we can calculate a running volume​ delta and ticks delta for the bar, which becomes the bar's final​ delta values when the bar closes (you can inspect values of elapsed realtime bars in the Data Window or the indicator's values). Note that these values will all reset if the script re-executes because of a change in inputs or a chart refresh. While this method of calculating is not perfect, it is by far the most precise way of calculating volume​ delta available on TradingView at the moment. Calculating more precise results would require scripts to have access to tick data from any chart timeframe. Charts at seconds timeframes do use exchange/broker ticks when the feeds you are using allow for it, and this indicator will run on them, but tick data is not yet available from higher timeframes. Also, note that the method used in this script is far superior to the intrabar inspection technique used on historical bars in my other "Delta Volume​" indicators. This is because volume​ and ticks delta here are calculated from many more realtime updates than the available intrabars in history. Unfortunately, the calculation method used here cannot be used on historical bars, where intrabar inspection remains, in my opinion, the optimal method. Inputs The script's inputs provide many ways to personalize all the components: what is displayed, the colors used to display the information, and the marker conditions. Tooltips provide details for many of the inputs; I leave their exploration to you. Markers Markers provide a way for you to identify the points of interest of your choice on the chart. You control the set of conditions that trigger each of the five available markers. You select conditions by entering, in the field for each marker, the number of each condition you want to include, separated by a comma. The conditions are:   1 —  The bar's polarity is up/dn​.   2 —  `close` rises/falls ("rises" means it is higher than its value on the previous bar).   3 —  DV's polarity is +/–.   4 —  DV% rises (↕).   5 —  POC rises/falls.   6 —  The quantity of realtime updates rises (↕).   7 —  DV​ > limit (You specify the limit in the inputs. Since DV​ can be +/–, DV– must be less than `–limit` for a short marker).   8 —  DV% > limit (↕).   9 —  DV+ rises for a long marker, DV– falls for a short.  10 —  Consecutive DV+/DV– on two bars.  11 —  Total volume rises (↕).  12 —  DT's polarity is +/–.  13 —  DT% rises (↕).  14 —  DT+ rises for a long marker, DT– falls for a short. Conditions showing the (↕) symbol do not have symmetrical states; they act more like filters. If you only include condition 4 in a marker's setup, for example, both long and short markers will trigger on bars where DV% rises. To trigger only long or short markers, you must add a condition providing directional differentiation, such as conditions 1 or 2. Accordingly, you would enter "1,4" or "2,4". For a marker to trigger, ALL the conditions you specified for it must be met. Long markers appear on the chart as "Mx▲" signs under the values displayed below candles. Short markers display "Mx▼" over the number of updates displayed above candles. The marker's number will replace the "x" in "Mx▲". The script loads with five markers that will not trigger because no conditions are associated with them. To activate markers, you will need to select and enter the set of conditions you require for each one. Alerts You can configure alerts on this script. They will trigger whenever one of the configured markers triggers. Alerts do not repaint, so they trigger at the bar's close—which is also when the markers will appear. █  HOW TO USE IT As a rule, I do not prescribe expected use of my indicators, as traders have proved to be much more creative than me in using them. Additionally, I tend to think that if you expect detailed recommendations from me to be able to use my indicators, it's a sign you are in a precarious situation and should go back to the drawing board and master the necessary basics that will allow you to explore and decide for yourself if my indicators can be useful to you, and how you will use them. I will make an exception for this thing, as it presents fairly novel information. I will use simple logic to surmise potential uses, as contrary to most of my other indicators, I have NOT used this one to actually trade. Markets have a way of throwing wrenches in our seemingly bullet-proof rationalizing, so drive cautiously and please forgive me if the pointers I share here don't pan out. The first thing to do is to disable your normal bars. You can do this by clicking on the eye icon that appears when you hover over the symbol's name in the upper-left corner of your chart. The absolute value and polarity of DV​ mean little without perspective; that's why I include both total volume​ for the bar and the percentage that DV​ represents of that total volume​. I interpret a low DV% value as indecision. If you share that opinion, you could, let's say, configure one of the markers on "DV% > 80%", for example (to do so you would enter "8" in the condition field of any marker, and "80" in the limit field for condition 8, below the marker conditions). I also like to analyze price action on the bar with DV%. Small DV% values should often produce small candle bodies. If a small DV% value occurs on a bar with much movement and high volume​, I'm thinking "tough battle with potential explosive power when one side wins". Conversely, large bodies with high DV% mean that large volume​ is breaching through multiple levels, or that nobody is suddenly willing to take the other side of a normal volume of trades. I find the POC lines really interesting. First, they tell us the price point where the most significant action (taking into account both price occurrences AND volume​) during the bar occurred. Second, they can be useful when compared against past values. Third, their color helps us in figuring out which ones are the most significant. Unsurprisingly, bunches of orange POCs tend to appear in consolidation zones, in pauses, and before reversals. It may be useful to often focus more on POC progression than on `close` values. This is not to say that OHLC values are not useful; looking, as is customary, for higher highs or lower lows, or for repeated tests of precise levels can of course still be useful. I do like how POCs add another dimension to chart readings. What should you do with the ticks delta above bars? Old-time ticker tape readers paid attention to the sounds coming from it (the "ticker" moniker actually comes from the sound they made). They knew activity was picking up when the frequency of the "ticks" increased. My thinking is that the total number of ticks will help you in the same way, since increasing updates usually mean growing interest—and thus perhaps price movement, as increasing volatility​ or volume​ would lead us to surmise. Ticks delta can help you figure out when proportionally large, random orders come in from traders with other perspectives than the short-term price action you are typically working with when you use this tool. Just as volume delta, ticks delta are one more informational component that can help you confirm convergence when building your opinions on price action. What are strong bars? They are an attempt to identify significance. They are like a default marker, except that instead of displaying "Mx▲/▼" below/above the bar, the candle's body is outlined in bright​ bull/bear color when one is detected. Strong bars require a respectable amount of conditions to be met (you can see and re-configure them in the inputs). Think of them as pushes rather than indications of an upcoming, strong and multi-bar move. Pushes do, for sure, often occur at the beginning of strong trends. You will often see a few strong bars occur at 2-3 bar intervals at the beginning or middle of trends. But they also tend to occur at tops/bottoms, which makes their interpretation problematic. Another pattern that you will see quite frequently is a final strong bar in the direction of the trend, followed a few bars later by another strong bar in the reverse direction. My summary analyses seemed to indicate these were perhaps good points where one could make a bet on an early, risky reversal entry. The last piece of information displayed by the indicator is the color of the candle bodies. Three possible colors are used. Bull/bear is determined by the polarity of DV​, but only when the bar's polarity matches that of DV​. When it doesn't, the color is the divergence color (orange, by default). Whichever color is used for the body, its intensity is determined by the DV% value. Maximum intensity occurs when DV%=100, so the more significant DV% values generate more noticeable colors. Body colors can be useful when looking to confirm the convergence of other components. The visual effect this creates hopefully makes it easier to detect patterns on the chart. One obvious methodology that comes to mind to trade with this tool would be to use another indicator like Technical Ratings at a higher timeframe to identify the larger context's trend, and then use this tool to identify entries for short-term trades in that direction. █  NOTES AND RAMBLINGS Instant Calculations This indicator uses instant values calculated on the bar only. No moving averages or calculations involving historical periods are used. The only exception to this rule is in some of the marker conditions like "Two consecutive DV+ values", where information from the previous bar is used. Trading Small vs Long Timeframes I never trade discretionary at the 5sec–5min timeframes this indicator was designed to be used with; I trade discretionary at 1D, 1W and 1M timeframes, and let systems trade at smaller timeframes. The higher the timeframe you trade at, the fewer fees you will pay because you trade less and are not churning trading volume​, as is inevitable at smaller timeframes. Trading at higher timeframes is also a good way to gain an instant edge on most of the trading crowd that has its nose to the ground and often tends to forget the big picture. It also makes for a much less demanding trading practice, where you have lots of time to research and build your long-term opinions on potential future outcomes. While the future is always uncertain, I believe trades riding on long-term trends have stronger underlying support from the reality outside markets. To traders who will ask why I publish an indicator designed for small timeframes, let me say that my main purpose here is to showcase what can be done with Pine. I often see comments by coders who are obviously not aware of what Pine is capable of in 2021. Since its humble beginnings seven years ago, Pine has grown and become a serious programming language. TradingView's growing popularity and its ongoing commitment to keep Pine accessible to newcomers to programming is gradually making Pine more and more of a standard in indicator and strategy programming. The technical barriers to entry for traders interested in owning their trading practice by developing their personal tools to trade have never been so low. I am also publishing this script because I value volume​ delta information, and I present here what I think is an original way of analyzing it. Performance The script puts a heavy load on the Pine runtime and the charting engine. After running the script for a while, you will often notice your chart becoming less responsive, and your chart tab can take longer to activate when you go back to it after using other tabs. That is the reason I encourage you to set the number of historical values displayed on bars to the minimum that meets your needs. When your chart becomes less responsive because the script has been running on it for many hours, refreshing the browser tab will restart everything and bring the chart's speed back up. You will then lose the information displayed on elapsed bars. Neutral Volume This script represents a departure from the way I have previously calculated volume​ delta in my scripts. I used the notion of "neutral volume" when inspecting intrabar timeframes, for bars where price did not move. No longer. While this had little impact​ when using intrabar inspection because the minimum usable timeframe was 1min (where bars with zero movement are relatively infrequent), a more precise way was required to handle realtime updates, where multiple consecutive prices often have the same value. This will usually happen whenever orders are unable to move across the bid/ask levels, either because of slow action or because a large-volume​ bid/ask level is taking time to breach. In either case, the proper way to calculate the polarity of volume​ delta for those updates is to use the last known polarity, which is how I calculate now. The Order Book Without access to the order book's levels (the depth of market), we are limited to analyzing transactions that come in the TradingView feed for the chart. That does not mean the volume​ delta information calculated this way is irrelevant; on the contrary, much of the information calculated here is not available in trading consoles supplied by exchanges/brokers. Yet it's important to realize that without access to the order book, you are forfeiting the valuable information that can be gleaned from it. The order book's levels are always in movement, of course, and some of the information they contain is mere posturing, i.e., attempts to influence the behavior of other players in the market by traders/systems who will often remove their orders when price comes near their order levels. Nonetheless, the order book is an essential tool for serious traders operating at intraday timeframes. It can be used to time entries/exits, to explain the causes of particular price movements, to determine optimal stop levels, to get to know the traders/systems you are betting against (they tend to exhibit behavioral patterns only recognizable through the order book), etc. This tool in no way makes the order book less useful; I encourage all intraday traders to become familiar with it and avoid trading without one.
Penunjuk Pine Script®
oleh LucF
101
Script Stopwatch - PineCoders FAQ█ WARNING The publication of our LibraryStopwatch has deprecated this publication. █ ORIGINAL DESCRIPTION This script calculates the run time of a Pine script. While its numbers are not very precise and it doesn’t work on all scripts, it will help developers calculate run times more precisely than by hand, and so provides Pine coders with an additional profiling tool to help them optimize their code. How to use the code • Place the code included between the up/down arrows after your script’s input() calls. • Comment out the display modes you don’t want to use. • Save your script, wait and look at the results. • Results show in different colors, depending on the average time per bar: - green for < 5 ms - dark red for < 50 ms - bright red for > 50 ms (the maximum allowed is 200). How the code works The code in this script starts by saving the value of the timenow variable on the first bar. While the time variable returns the time at the beginning of the bar, timenow returns the current time. The code then follows the progression of timenow during the script’s execution. The variable only updates every second, so in between updates the script makes an estimate of the total time elapsed by adding the last average time per bar calculated to each bar that passes until timenow increases by another 1000 because one more second has elapsed since its last update. At that point a new, current average time per bar is calculated and the cycle repeats. The code only calculates elapsed time for the initial run. Once the realtime bar is hit, timing stops so that time spent in the realtime bar does not affect the numbers once they have been calculated on the script’s initial pass over the dataset. Notes • If results show zero elapsed time, it’s most probably because your script executes in less than one second, which is very good. In that case timenow hasn’t changed, so no timing can be calculated. • The code is quirky and doesn’t work on all scripts. • It doesn’t properly time execution of security() calls. • The average time per bar will sometimes vary quite a bit with changes in chart resolution. Look first. Then leap.
Penunjuk Pine Script®
oleh PineCoders
9
Information-Geometric Market DynamicsInformation-Geometric Market Dynamics The Information Field: A Geometric Approach to Market Dynamics By: DskyzInvestments Foreword: Beyond the Shadows on the Wall If you have traded for any length of time, you know " the feeling ." It is the frustration of a perfect setup that fails, the whipsaw that stops you out just before the real move, the nagging sense that the chart is telling you only half the story. For decades, technical analysis has relied on interpreting the shadows—the patterns left behind by price. We draw lines on these shadows, apply indicators to them, and hope they reveal the future. But what if we could stop looking at the shadows and, instead, analyze the object casting them? This script introduces a new paradigm for market analysis: Information-Geometric Market Dynamics (IGMD) . The core premise of IGMD is that the price chart is merely a one-dimensional projection of a much richer, higher-dimensional reality—an " information field " generated by the collective actions and beliefs of all market participants. This is not just another collection of indicators. It is a unified framework for measuring the geometry of the market's information field—its memory, its complexity, its uncertainty, its causal flows—and making high-probability decisions based on that deeper reality. By fusing advanced mathematical and informational concepts, IGMD provides a multi-faceted lens through which to view market behavior, moving beyond simple price action into the very structure of market information itself. Prepare to move beyond the flatland of the price chart. Welcome to the information field. The IGMD Framework: A Multi-Kernel Approach What is a Kernel? The Heart of Transformation In mathematics and data science, a kernel is a powerful and elegant concept. At its core, a kernel is a function that takes complex, often inscrutable data and transforms it into a more useful format. Think of it as a specialized lens or a mathematical "probe." You cannot directly measure abstract concepts like "market memory" or "trend quality" by looking at a price number. First, you must process the raw price data through a specific mathematical machine—a kernel—that is designed to output a measurement of that specific property. Kernels operate by performing a sort of "similarity test," projecting data into a higher-dimensional space where hidden patterns and relationships become visible and measurable. Why do creators use them? We use kernels to extract features —meaningful pieces of information—that are not explicitly present in the raw data. They are the essential tools for moving beyond surface-level analysis into the very DNA of market behavior. A simple moving average can tell you the average price; a suite of well-chosen kernels can tell you about the character of the price action itself. The Alchemist's Challenge: The Art of Fusion Using a single kernel is a challenge. Using five distinct, computationally demanding mathematical engines in unison is an immense undertaking. The true difficulty—and artistry—lies not just in using one kernel, but in fusing the outputs of many . Each kernel provides a different perspective, and they can often give conflicting signals. One kernel might detect a strong trend, while another signals rising chaos and uncertainty. The IGMD script's greatest strength is its ability to act as this alchemist, synthesizing these disparate viewpoints through a weighted fusion process to produce a single, coherent picture of the market's state. It required countless hours of testing and calibration to balance the influence of these five distinct analytical engines so they work in harmony rather than cacophony. The Five Kernels of Market Dynamics The IGMD script is built upon a foundation of five distinct kernels, each chosen to probe a unique and critical dimension of the market's information field. 1. The Wavelet Kernel (The "Microscope") What it is: The Wavelet Kernel is a signal processing function designed to decompose a signal into different frequency scales. Unlike a Fourier Transform that analyzes the entire signal at once, the wavelet slides across the data, providing information about both what frequencies are present and when they occurred. The Kernels I Use: Haar Kernel: The simplest wavelet, a square-wave shape defined by the coefficients . It excels at detecting sharp, sudden changes. Daubechies 2 (db2) Kernel: A more complex and smoother wavelet shape that provides a better balance for analyzing the nuanced ebb and flow of typical market trends. How it Works in the Script: This kernel is applied iteratively. It first separates the finest "noise" (detail d1) from the first level of trend (approximation a1). It then takes the trend a1 and repeats the process, extracting the next level of cycle (d2) and trend (a2), and so on. This hierarchical decomposition allows us to separate short-term noise from the long-term market "thesis." 2. The Hurst Exponent Kernel (The "Memory Gauge") What it is: The Hurst Exponent is derived from a statistical analysis kernel that measures the "long-term memory" or persistence of a time series. It is the definitive measure of whether a series is trending (H > 0.5), mean-reverting (H < 0.5), or random (H = 0.5). How it Works in the Script: The script employs a method based on Rescaled Range (R/S) analysis. It calculates the average range of price movements over increasingly larger time lags (m1, m2, m4, m8...). The slope of the line plotting log(range) vs. log(lag) is the Hurst Exponent. Applying this complex statistical analysis not to the raw price, but to the clean, wavelet-decomposed trend lines, is a key innovation of IGMD. 3. The Fractal Dimension Kernel (The "Complexity Compass") What it is: This kernel measures the geometric complexity or "jaggedness" of a price path, based on the principles of fractal geometry. A straight line has a dimension of 1; a chaotic, space-filling line approaches a dimension of 2. How it Works in the Script: We use a version based on Ehlers' Fractal Dimension Index (FDI). It calculates the rate of price change over a full lookback period (N3) and compares it to the sum of the rates of change over the two halves of that period (N1 + N2). The formula d = (log(N1 + N2) - log(N3)) / log(2) quantifies how much "longer" and more convoluted the price path was than a simple straight line. This kernel is our primary filter for tradeable (low complexity) vs. untradeable (high complexity) conditions. 4. The Shannon Entropy Kernel (The "Uncertainty Meter") What it is: This kernel comes from Information Theory and provides the purest mathematical measure of information, surprise, or uncertainty within a system. It is not a measure of volatility; a market moving predictably up by 10 points every bar has high volatility but zero entropy . How it Works in the Script: The script normalizes price returns by the ATR, categorizes them into a discrete number of "bins" over a lookback window, and forms a probability distribution. The Shannon Entropy H = -Σ(p_i * log(p_i)) is calculated from this distribution. A low H means returns are predictable. A high H means returns are chaotic. This kernel is our ultimate gauge of market conviction. 5. The Transfer Entropy Kernel (The "Causality Probe") What it is: This is by far the most advanced and computationally intensive kernel in the script. Transfer Entropy is a non-parametric measure of directed information flow between two time series. It moves beyond correlation to ask: "Does knowing the past of Volume genuinely reduce our uncertainty about the future of Price?" How it Works in the Script: To make this work, the script discretizes both price returns and the chosen "driver" (e.g., OBV) into three states: "up," "down," or "neutral." It then builds complex conditional probability tables to measure the flow of information in both directions. The Net Transfer Entropy (TE Driver→Price minus TE Price→Driver) gives us a direct measure of causality . A positive score means the driver is leading price, confirming the validity of the move. This is a profound leap beyond traditional indicator analysis. Chapter 3: Fusion & Interpretation - The Field Score & Dashboard Each kernel is a specialist providing a piece of the puzzle. The Field Score is where they are fused into a single, comprehensive reading. It's a weighted sum of the normalized scores from all five kernels, producing a single number from -1 (maximum bearish information field) to +1 (maximum bullish information field). This is the ultimate "at-a-glance" metric for the market's net state, and it is interpreted through the dashboard. The Dashboard: Your Mission Control Field Score & Regime: The master metric and its plain-English interpretation ("Uptrend Field", "Downtrend Field", "Transitional"). Kernel Readouts (Wave Align, H(w), FDI, etc.): The live scores of each individual kernel. This allows you to see why the Field Score is what it is. A high Field Score with all components in agreement (all green or red) is a state of High Coherence and represents a high-quality setup. Market Context: Standard metrics like RSI and Volume for additional confluence. Signals: The raw and adjusted confluence counts and the final, calculated probability scores for potential long and short entries. Pattern: Shows the dominant candlestick pattern detected within the currently forming APEX range box and its calculated confidence percentage. Chapter 4: Mastering the Controls - The Inputs Menu Every parameter is a lever to fine-tune the IGMD engine. 📊 Wavelet Transform: Kernel ( Haar for sharp moves, db2 for smooth trends) and Scales (depth of analysis) let you tune the script's core microscope to your asset's personality. 📈 Hurst Exponent: The Window determines if you're assessing short-term or long-term market memory. 🔍 Fractal Dimension & ⚡ Entropy Volatility: Adjust the lookback windows to make these kernels more or less sensitive to recent price action. Always keep "Normalize by ATR" enabled for Entropy for consistent results. 🔄 Transfer Entropy: Driver lets you choose what causal force to measure (e.g., OBV, Volume, or even an external symbol like VIX). The throttle setting is a crucial performance tool, allowing you to balance precision with script speed. ⚡ Field Fusion • Weights: This is where you can customize the model's "brain." Increase the weights for the kernels that best align with your trading philosophy (e.g., w_hurst for trend followers, w_fdi for chop avoiders). 📊 Signal Engine: Mode offers presets from Conservative to Aggressive . Min Confluence sets your evidence threshold. Dynamic Confluence is a powerful feature that automatically adapts this threshold to the market regime. 🎨 Visuals & 📏 Support/Resistance: These inputs give you full control over the chart's appearance, allowing you to toggle every visual element for a setup that is as clean or as data-rich as you desire. Chapter 5: Reading the Battlefield - On-Chart Visuals Pattern Boxes (The Large Rectangles): These are not simple range boxes. They appear when the Field Score crosses a significance threshold, signaling a potential ignition point. Color: The color reflects the dominant candlestick pattern that has occurred within that box's duration (e.g., green for Bull Engulf). Label: Displays the dominant pattern, its duration in bars, and a calculated Confidence % based on field strength and pattern clarity. Bar Pattern Boxes (The Small Boxes): If enabled, these highlight individual, significant candlestick patterns ( BE for Bull Engulf, H for Hammer) on a bar-by-bar basis. Signal Markers (▲ and ▼): These appear only when the Signal Engine's criteria are all met. The number is the calculated Probability Score . RR Rails (Dashed Lines): When a signal appears, these lines automatically plot the Entry, Stop Loss (based on ATR), and two Take Profit targets (based on Risk/Reward ratios). They dynamically break and disappear as price touches each level. Support & Resistance Lines: Plots of the highest high ( Resistance ) and lowest low ( Support ) over a lookback, providing key structural levels. Chapter 6: Development Philosophy & A Final Word One single question: " What is the market really doing? " It represents a triumph of complexity, blending concepts from signal processing, chaos theory, and information theory into a cohesive framework. It is offered for educational and analytical purposes and does not constitute financial advice. Its goal is to elevate your analysis from interpreting flat shadows to measuring the rich, geometric reality of the market's information field. As the great mathematician Benoit Mandelbrot , father of fractal geometry, noted: "Clouds are not spheres, mountains are not cones, coastlines are not circles, and bark is not smooth, nor does lightning travel in a straight line." Neither does the market. IGMD is a tool designed to navigate that beautiful, complex, and fractal reality. — Dskyz, Trade with insight. Trade with anticipation.
Penunjuk Pine Script®
oleh DskyzInvestments
9
Session Bar/Candle ColoringChange the color of candles within a user-defined trading session. Borders and wicks can be changed as well, not just the body color. PREFACE This script can be used an educational resource for those who are interested in learning Pine Script. Therefore, the script is published open source and is organized in a manner that follows the recommended Style Guide . While the main premise of the indicator is rather simple, the script showcases various things that can be achieved such as conditional plotting, alignment of indicator settings, user input validation, script optimization, and more. The script also has examples of taking into consideration the chart timeframe and/or different chart types (Heikin Ashi, Renko, etc.) that a user might be running it on. Note: for complete beginners, I strongly suggest going through the Pine Script User Manual (possibly more than once). FEATURES Besides being able to select a specific time window, the indicator also provides additional color settings for changing the background color or changing the colors of neutral/indecisive candles, as shown in the image below. This allows for a higher level of customization beyond the TradingView chart settings or other similar scripts that are currently available. HOW TO USE First, define the intraday trading session that will contain the candles to modify. The session can be limited to specific days of the week. Next, select the parts of the candles that should be modified: Body, Borders, Wick, and/or Background. For each of the candle parts that were enabled, you can select the colors that will be used depending on whether a candle is bullish (⇧), bearish (⇩), or neutral (⇆). All other indicator settings will have a detailed tooltip to describe its usage and/or effect. LIMITATIONS The indicator is not intended to function on Daily or higher timeframes due to the intraday nature of session time windows. The indicator cannot always automatically detect the chart type being used, therefore the user is requested to manually input the chart type via the " Chart Style " setting. Depending on the available historical data and the selected choice for the " Portion of bar in session " setting, the indicator may not be able to update very old candles on the chart. EXAMPLE USAGE This section will show examples of different scenarios that the indicator can be used for. Emphasizing a main trading session. Defining a "Pre/post market hours background" like is available for some symbols (e.g., NASDAQ:AAPL ). Highlighting in which bar the midnight candle occurs. Hiding indecision bars (neutral candles). Showing only "Regular Trading Hours" for a chart that does not have the option to toggle ETH/RTH. To achieve this, the actual chart data is hidden, and only the indicator is visible; alternatively, a 2nd instance of the indicator could change colors to match the chart background. Using a combination of Bars and Japanese Candlesticks. Alternatively, this could be done by hiding the main chart data and using 2 instances of the indicator (one with " Chart Style " setting as Bars , and the other set to Candles ). Using a combination of thin and thick bars on Range charts. Note: requires disabling the "Thin Bars" setting for Bar charts in the TradingView chart settings. NOTES If using more than one instance of this indicator on the same chart, you can use the TradingView "Save Indicator Template" feature to avoid having to re-configure the multiple indicators at a later time. This indicator is intended to work "out-of-the-box" thanks to the behind_chart option introduced to Pine Script in October 2024. But you can always manually bring the indicator to the front just in case the color changes are not being seen (using the "More" option in the indicator status line: More > Visual Order > Bring to front ). Many thanks to fikira for their help and inspiring me to create open source scripts. Any feedback including bug reports or suggestions for improving the indicator (or source code itself) are always welcome in the comments section.
Penunjuk Pine Script®
oleh n00btraders
12
Dual Dynamic Fibonacci Retracement — Long and Short Duration Title : "The Dual-Dynamic Fibonacci Retracement Script: An Advanced Tool for Comprehensive Market Analysis" As the author of the "Dual-Dynamic Fibonacci Retracement Script", I am delighted to introduce you to this cutting-edge tool for technical analysis. Unlike conventional Fibonacci scripts, this advanced model incorporates multiple unique features and adjustments that make it a powerful asset for any market analyst. Whether you're dealing with forex, commodities, equities or any other market, this script is versatile enough to enhance your trading strategy. Uniqueness & Differentiation: The "Dual-Dynamic Fibonacci Script" stands out by offering two distinct lookback periods. This feature is what separates it from other scripts available in the market. The first lookback period is longer, focusing on capturing broader market trends. The second lookback period is shorter, allowing for a more granular analysis of near-term market fluctuations. This dual perspective provides a more comprehensive view of the market, allowing you to see both the forest and the trees at the same time. Fibonacci Levels: While offering the standard Fibonacci retracement levels (0.236, 0.382, 0.5, 0.618, 0.786, and 1.0), the script also gives you the ability to plot 0.114 and 0.886 levels. These additional levels offer an extra layer of depth to your analysis, and can prove crucial in high-volatility markets where they often serve as significant support and resistance points. Customizable Line Shifts and Extends: This script provides options for customization of the shift and extension of the plotted lines. This means you can adjust the start and end points of the Fibonacci lines according to your personal trading style and strategy. This level of personalization is not typically available in other scripts, and it allows for a more tailored visual representation. Flexible Trading Positioning: Depending on whether the closing price is above or below the midpoint of the pivot high and pivot low, the Fibonacci retracement levels are adjusted accordingly. This ensures the script remains relevant and useful regardless of market conditions. Clean Visualization: To prevent clutter and maintain focus on the most relevant price action, the script removes old Fibonacci lines and plots new ones once a new pivot high or low is identified. This clean visualization helps keep your analysis focused and sharp. How to Use the Script: To get started, simply adjust the lookback periods according to your trading strategy. If you're a long-term investor or prefer swing trading, a longer lookback period might be appropriate. Conversely, if you're a day trader, a shorter lookback period might be more beneficial. The "Shift" and "Extend" inputs allow you to control the positioning of the Fibonacci lines on your chart. Positive values shift the lines to the right, while negative values shift them to the left. You also have the choice to plot the additional Fibonacci levels (0.114 and 0.886) via the "Plot 0.114 and 0.886 levels?" input. Similarly, the "Plot second set of levels?" input lets you decide whether to display the second set of Fibonacci levels derived from the shorter lookback period. Like any technical analysis tool, this script is most effective when used in conjunction with other indicators and methods of analysis. It is designed to work well in trending markets, where Fibonacci retracements can often indicate potential reversal levels. However, it's always recommended to use a holistic approach to market analysis to maximize the likelihood of successful trades. Note: the two lines drawn on the chart are there to help the user identify the levels from which the two respective Fib sequences are calculated. ~~~ Input Explanations: Long Period Pivot High/Low Lookback and Short Period Pivot High/Low Lookback : These settings determine the length of the lookback periods for the long-term and short-term pivot points, respectively. A pivot point is a technical analysis indicator used to determine the overall trend of the market over different time frames. The pivot points are then used to calculate the Fibonacci levels. A longer lookback period will identify pivot points over a broader time frame, capturing major market trends, while a shorter lookback period will identify pivot points over a narrower time frame, capturing more immediate market movements. Long Period Fibonacci Level Shift and Short Period Fibonacci Level Shift : These inputs control the shift of the Fibonacci levels based on the long and short lookback periods, respectively. If you want to shift the Fibonacci levels to the right, increase the value. If you want to shift the Fibonacci levels to the left, decrease the value. This allows you to adjust the Fibonacci levels to better align with your analysis. Long Period Fibonacci Level Extend and Short Period Fibonacci Level Extend : These inputs control the extension of the Fibonacci levels based on the long and short lookback periods, respectively. If you want the Fibonacci levels to extend further to the right, increase the value. If you want the Fibonacci levels to extend less to the right, decrease the value. This feature provides the flexibility to adjust the length of the Fibonacci levels according to your personal trading preferences and strategy. Plot 0.114 and 0.886 levels? : This setting gives you the ability to plot the additional 0.114 and 0.886 Fibonacci levels. These levels provide extra depth to your analysis, particularly in highly volatile markets where they can act as significant support and resistance levels. Plot second set of levels? : This input allows you to decide whether to plot the second set of Fibonacci levels based on the short lookback period. Displaying this second set of levels can provide a more granular view of market movements and potential reversal points, enhancing your overall analysis.
Penunjuk Pine Script®
oleh FadingExtremes
2
GIGANEVA V6.61 PublicThis enhanced Fibonacci script for TradingView is a powerful, all-in-one tool that calculates Fibonacci Levels, Fans, Time Pivots, and Golden Pivots on both logarithmic and linear scales. Its ability to compute time pivots via fan intersections and Range interactions, combined with user-friendly features like Bool Fib Right, sets it apart. The script maximizes TradingView’s plotting capabilities, making it a unique and versatile tool for technical analysis across various markets. 1. Overview of the Script The script appears to be a custom technical analysis tool built for TradingView, improving upon an existing script from TradingView’s Community Scripts. It calculates and plots: Fibonacci Levels: Standard retracement levels (e.g., 0.236, 0.382, 0.5, 0.618, etc.) based on a user-defined price range. Fibonacci Fans: Trendlines drawn from a high or low point, radiating at Fibonacci ratios to project potential support/resistance zones. Time Pivots: Points in time where significant price action is expected, determined by the intersection of Fibonacci Fans or their interaction with key price levels. Golden Pivots: Specific time pivots calculated when the 0.5 Fibonacci Fan (on a logarithmic or linear scale) intersects with its counterpart. The script supports both logarithmic and linear price scales, ensuring versatility across different charting preferences. It also includes a feature to extend Fibonacci Fans to the right, regardless of whether the user selects the top or bottom of the range first. 2. Key Components Explained a) Fibonacci Levels and Fans from Top and Bottom of the "Range" Fibonacci Levels: These are horizontal lines plotted at standard Fibonacci retracement ratios (e.g., 0.236, 0.382, 0.5, 0.618, etc.) based on a user-defined price range (the "Range"). The Range is typically the distance between a significant high (top) and low (bottom) on the chart. Example: If the high is $100 and the low is $50, the 0.618 retracement level would be at $80.90 ($50 + 0.618 × $50). Fibonacci Fans: These are diagonal lines drawn from either the top or bottom of the Range, radiating at Fibonacci ratios (e.g., 0.382, 0.5, 0.618). They project potential dynamic support or resistance zones as price evolves over time. From Top: Fans drawn downward from the high of the Range. From Bottom: Fans drawn upward from the low of the Range. Log and Linear Scale: Logarithmic Scale: Adjusts price intervals to account for percentage changes, which is useful for assets with large price ranges (e.g., cryptocurrencies or stocks with exponential growth). Fibonacci calculations on a log scale ensure ratios are proportional to percentage moves. Linear Scale: Uses absolute price differences, suitable for assets with smaller, more stable price ranges. The script’s ability to plot on both scales makes it adaptable to different markets and user preferences. b) Time Pivots Time pivots are points in time where significant price action (e.g., reversals, breakouts) is anticipated. The script calculates these in two ways: Fans Crossing Each Other: When two Fibonacci Fans (e.g., one from the top and one from the bottom) intersect, their crossing point represents a potential time pivot. This is because the intersection indicates a convergence of dynamic support/resistance zones, increasing the likelihood of a price reaction. Example: A 0.618 fan from the top crosses a 0.382 fan from the bottom at a specific bar on the chart, marking that bar as a time pivot. Fans Crossing Top and Bottom of the Range: A fan line (e.g., 0.5 fan from the bottom) may intersect the top or bottom price level of the Range at a specific time. This intersection highlights a moment where the fan’s projected support/resistance aligns with a key price level, signaling a potential pivot. Example: The 0.618 fan from the bottom reaches the top of the Range ($100) at bar 50, marking bar 50 as a time pivot. c) Golden Pivots Definition: Golden pivots are a special type of time pivot calculated when the 0.5 Fibonacci Fan on one scale (logarithmic or linear) intersects with the 0.5 fan on the opposite scale (or vice versa). Significance: The 0.5 level is the midpoint of the Fibonacci sequence and often acts as a critical balance point in price action. When fans at this level cross, it suggests a high-probability moment for a price reversal or significant move. Example: If the 0.5 fan on a logarithmic scale (drawn from the bottom) crosses the 0.5 fan on a linear scale (drawn from the top) at bar 100, this intersection is labeled a "Golden Pivot" due to its confluence of key Fibonacci levels. d) Bool Fib Right This is a user-configurable setting (a boolean input in the script) that extends Fibonacci Fans to the right side of the chart. Functionality: When enabled, the fans project forward in time, regardless of whether the user selected the top or bottom of the Range first. This ensures consistency in visualization, as the direction of the Range selection (top-to-bottom or bottom-to-top) does not affect the fan’s extension. Use Case: Traders can use this to project future support/resistance zones without worrying about how they defined the Range, improving usability. 3. Why Is This Code Unique? Original calculation of Log levels were taken from zekicanozkanli code. Thank you for giving me great Foundation, later modified and applied to Fib fans. The script’s uniqueness stems from its comprehensive integration of Fibonacci-based tools and its optimization for TradingView’s plotting capabilities. Here’s a detailed breakdown: All-in-One Fibonacci Tool: Most Fibonacci scripts on TradingView focus on either retracement levels, extensions, or fans. This script combines: Fibonacci Levels: Static horizontal lines for retracement and extension. Fibonacci Fans: Dynamic trendlines for projecting support/resistance. Time Pivots: Temporal analysis based on fan intersections and Range interactions. Golden Pivots: Specialized pivots based on 0.5 fan confluences. By integrating these functions, the script provides a holistic Fibonacci analysis tool, reducing the need for multiple scripts. Log and Linear Scale Support: Many Fibonacci tools are designed for linear scales only, which can distort projections for assets with exponential price movements. By supporting both logarithmic and linear scales, the script caters to a wider range of markets (e.g., stocks, forex, crypto) and user preferences. Time Pivot Calculations: Calculating time pivots based on fan intersections and Range interactions is a novel feature. Most TradingView scripts focus on price-based Fibonacci levels, not temporal analysis. This adds a predictive element, helping traders anticipate when significant price action might occur. Golden Pivot Innovation: The concept of "Golden Pivots" (0.5 fan intersections across scales) is a unique addition. It leverages the symmetry of the 0.5 level and the differences between log and linear scales to identify high-probability pivot points. Maximized Plot Capabilities: TradingView imposes limits on the number of plots (lines, labels, etc.) a script can render. This script is coded to fully utilize these limits, ensuring that all Fibonacci levels, fans, pivots, and labels are plotted without exceeding TradingView’s constraints. This optimization likely involves efficient use of arrays, loops, and conditional plotting to manage resources while delivering a rich visual output. User-Friendly Features: The Bool Fib Right option simplifies fan projection, making the tool intuitive even for users who may not consistently select the Range in the same order. The script’s flexibility in handling top/bottom Range selection enhances usability. 4. Potential Use Cases Trend Analysis: Traders can use Fibonacci Fans to identify dynamic support/resistance zones in trending markets. Reversal Trading: Time pivots and Golden Pivots help pinpoint moments for potential price reversals. Range Trading: Fibonacci Levels provide key price zones for trading within a defined range. Cross-Market Application: Log/linear scale support makes the script suitable for stocks, forex, commodities, and cryptocurrencies. The original code was from zekicanozkanli . Thank you for giving me great Foundation.
Penunjuk Pine Script®
oleh AutomatedTradingAlgorithms
Volatility Adaptive Signal Tracker (VAST)The Adaptive Trend Following Buy/Sell Signals Pine Script is designed to help traders identify and capitalize on market trends using an adaptive trend-following strategy. This script focuses on generating reliable buy and sell signals by analyzing market trends and volatility. It simplifies the trading process by providing clear signals without plotting additional lines, making it easy to use and interpret. Key Features: Adaptive Trend Following: The script employs an adaptive trend-following approach that leverages market volatility to generate buy and sell signals. This method is effective in both trending and volatile markets. Inputs and Customization: The script includes customizable parameters for the Simple Moving Average (SMA) length, the Average True Range (ATR) length, and the ATR multiplier. These inputs allow traders to adjust the sensitivity of the signals to match their trading style and market conditions. Signal Generation: Buy Signal: Generated when the closing price crosses above the upper adaptive band, indicating a potential upward trend. Sell Signal: Generated when the closing price crosses below the lower adaptive band, indicating a potential downward trend. Visual Signals: The script uses plotshape to mark buy signals with green labels below the bars and sell signals with red labels above the bars. This clear visual representation helps traders quickly identify trading opportunities. Alert Conditions: The script sets up alert conditions for both buy and sell signals. Traders can use these alerts to receive notifications when a signal is generated, ensuring they do not miss any trading opportunities. How It Works: SMA Calculation: The script calculates the Simple Moving Average (SMA) over a specified period, which helps in identifying the general trend direction. ATR Calculation: The Average True Range (ATR) is calculated to measure market volatility. Adaptive Bands: Upper and lower adaptive bands are created by adding and subtracting a multiple of the ATR to the SMA, respectively. Signal Logic: Buy signals are generated when the closing price crosses above the upper band, while sell signals are generated when the closing price crosses below the lower band. Example Use Case: A trader looking to capitalize on medium-term trends in the Nifty futures market can use this script to receive timely buy and sell signals. By customizing the SMA length and ATR parameters, the trader can fine-tune the script to match their trading strategy, ensuring they enter and exit trades at optimal points. Benefits: Simplicity: The script provides clear buy and sell signals without cluttering the chart with additional lines or indicators. Adaptability: Customizable parameters allow traders to adapt the script to various market conditions and trading styles. Alerts: Built-in alert conditions ensure traders receive timely notifications, helping them to act quickly on trading signals. How to Use: Open TradingView: Go to the TradingView website and log in. Create a New Chart: Click on the “Chart” button to open a new chart. Open the Pine Script Editor: Click on the “Pine Editor” tab at the bottom of the chart. Create a New Script: Delete any default code in the Pine Script editor and paste the provided script. Add to Chart: Click on the “Add to Chart” button to compile and add the script to your chart. Save the Script: Click “Save” and name the script. Set Alerts: Right-click on the chart, select “Add Alert,” and choose the appropriate condition to set alerts for buy and sell signals.
Penunjuk Pine Script®
oleh Shreeyash_Chiddarwar
Psychological levels (Bank levels) PsychoLevels v2 - TartigradiaPsychological levels (Bank levels) plots "round" price levels above and below current price, by truncating after the nth leftmost digits, based on neuroscience research of how humans intuitively calculate in logarithms. Psychological levels, also called bank levels, are "round" price numbers around which price often experience resistance or support, because traders and investors tend to set orders around these round numbers. Calculation here is fully automatic and dynamic, contrary to other similar scripts, this one uses a mathematical calculation that extracts the 1, 2 or 3 leftmost digits and calculate the previous and next level by incrementing/decrementing these digits. This means it works for any symbol under any price range. This approach is based on neuroscience research, which found that human brains intuitively approximate numbers on a logarithmic scale, adults and children alike, and similarly to macaques, for more info see Numerical Cognition , Weber-Fechner Law , Zipf law. For example, if price is at 0.0421, the next major price level is 0.05 and medium one is 0.043. For another asset currently priced at 19354, the next and previous major price levels are 20000 and 10000 respectively, and the next/previous medium levels are 20000 and 19000, and the next/previous weak levels are 19400 and 19300. Usage: * By default, strong upper level is in green, strong lower level is in red, medium upper level is in blue, medium lower level is in yellow, and weak levels aren't displayed but can be. Half levels are also displayed, in a darker color. Strong levels are increments of the first leftmost digit (eg, 10000 to 20000), medium levels are increments of the second leftmost digit (eg, 19000 to 20000), and weak levels of the third leftmost digit (eg, 19100 to 19200). Instead of plotting all the psychological levels all at once as a grid, which makes the chart unintelligible, here the levels adapt dynamically around the current price, so that they show the upper/lower levels relatively to the current price. * A simple moving average is implemented, so that "half-levels" are also displayed when relevant (eg, medium level can also display 19500 instead of only 19000 or 20000). This can be disabled by setting smoothing to 1. * By default, the script runs on the daily timeframe, whatever the current chart's timeframe is. This is to reduce the variability in levels, to make it less noisy than intraday price movement, but this can be changed in the settings. * The step can be adjusted to increase the gap between levels, eg, if you want to display one every 2 levels then input step = 2 (eg, 22000, 24000, 26000, etc), or if you want to display quarter levels, input 0.25 (eg, 22000, 22250, 22500, etc). The default values should fit most use cases and cover most psychological levels. I made this script mainly to train with PineScript, but I found it surprisingly accurate to define levels that are respected by price movements. So I guess it can be useful for new traders and experienced traders alike, as it's easy to forget that psychological levels can often be as strong if not stronger than technical levels. It can also be used to quickly screen other minor assets for trading opportunities. For example, a hybrid strategy would be to manually define levels on BTCUSD but using this script to automatically define levels in crypto altcoins and quickly screen them for a trade opportunity that can be greater than with BTCUSD but with the same trend. Changes compared to v1: * Deduplicated redundant calculations and hence faster script. * Added half-step levels, which allows to more easily see breakouts (because the levels are still on-screen). * All steps are now configuration on the GUI. * Revamped color scheme. * And major reasons to post as a separate v2 script rather than updating: because we can't update the original description nor screenshot. I have now read more about the House Rules and saw other scriptmakers, so I am trying to write better descriptions like wizards do, by explaining not only how the script works but what the underlying financial concept is to a neophyte audience.
Penunjuk Pine Script®
oleh tartigradia
3
Adapting a built-in [PineCoders]█  OVERVIEW This Pine script shows how it can be quite simple to personalize a built-in indicator for your needs. █  OUR SCRIPT Our objective was to add the current values for volume​ and its moving average in prominent view, and use brighter colors than the built-in. We started with the source code from the "Volume" built-in indicator. You can access the source code of many built-ins from the Pine Editor by clicking the "Open" button and choosing "New default built-in script..." We changed the variable names so they conform to our Coding Conventions . Everybody is of course free to code their scripts the way they want; the conventions provide guidelines for those interested in Pine-specific recommendations. We use our conventions to make our code more readable, which helps readers of open-source publications. As Uncle Bob, a.k.a. Robert Cecil Martin, argues in his "Clean Code" book, code that is easier to read is also useful for its first user: you. We assigned the colors we use to constants because they are used in multiple places in the script. If we decide to change them, we only need to change the constant definitions for the change to trickle down to the rest of the code. We used the `inline` and `tooltip` parameters of input() to better organize our inputs and provide extra information under an "i" icon when needed. We wanted to pack more information in the display of the moving average and volume​ than just the values, so we color-coded their background:  • When the MA is rising, the background of its table cell is in the bull color, otherwise it's in the bear color. The period used for the MA is also displayed in that cell's legend.  • When the current volume's value is higher/lower than its MA, the background of its cell is of bull/bear color. We use a Pine table to display our values. We use extra cells to provide a configurable margin to the left, and a small space between the two values. Because we only use constant colors in this script (i.e., values that are known at compile time), users can change the colors in the "Setting/Style" tab's color widgets. Users of the script can also use the tab to change other attributes of the plots. Look first. Then leap.
Penunjuk Pine Script®
oleh PineCoders
21
Point and Figure Chart - LiveHello Traders, This is "Point and Figure Chart (PnF)" script that run in separated window in real time. The separated PnF chart window is timeless, so no relation with the time on the chart. PnF chart consist of "X" and "O" columns. While "X" columns represents rising prices, "O" column represents a falling price. If you have no idea about what PnF charting is then you should search for "Point and Figure Charting" on the net and get some info before using this script. Now lets talk about details. PnF Chart requires at least two variables to be set => Box size and Reversal. Box size represents the size of each X/O in PnF chart and the reversal is used to calculate new X/O or reversal. for example if currrent column is X column then for new "X", "box size * 1" move is needed and for new "O" column or reversal, "box size * revelsal" move is needed. in the script I use lines as X/O columns. In the options you can set "Box Size Assingment Method". you have 3 options Traditional, ATR, Percentage . what are they? Traditional: user-defined box size, means you can set the box size as you wish, using the option . if you use this option then you should set it accordingly. ATR : that's dynamic box size scaling and on each columns it's calculated once, you can set length for ATR Percentage: that's also dynamic box size scaling according to closing price when new column appeared. if you use this option then you should set it accordingly. Reversal: The reversal is typically 3 but you can change it as you wish "Change Bar Color by PnF Trend": if you enable this option then bar color changes by PnF columns, by default it's not enabled "Change Column Color When Breakout Occurs": PnF color changes if Double Top/Bottom breakout accours. enabled by default and you can set the colors as you wish using the options "Change Bar Color When Breakout Occurs": bar colors changed if Double Top/Bottom breakout accours. enabled by default and you can set the colors as you wish using the options the script checks only Double Top/Bottom breakouts at the moment. there are many other breakouts such Triple/Quadruple, Ascending/Descending Triple Top/Bottom breakouts, Catapult etc. Also the script shows new X/O level and reversal Levels in PnF window. An example: If you enable "Change Bar Color by PnF Trend" option: An example if you disable the option "Change Column Color When Breakout Occurs You may want to see my another/older "Point and Point Chart" script as well. you can find it in my profile/published scripts and in the Public Library. I use same PnF calculation algorithm in both scripts. Enjoy!
Penunjuk Pine Script®
oleh LonesomeTheBlue
28
GTrader-ICT All In One-Comumnity VersionMeet the **GTrader-ICT All In One **, a comprehensive toolkit designed to integrate key Inner Circle Trader (ICT) concepts directly onto your chart. This powerful overlay indicator consolidates multiple essential tools, streamlining your technical analysis and helping you identify key temporal and price-based events. 📚 References & Inspiration This indicator stands on the shoulders of giants. With the help of **tradeforopp** and **LuxAlgo**. The concepts and some implementation details were referenced from the following excellent, publicly available scripts: ICT Killzones: The session drawing and pivot logic is adapted from tradeforopp ICT Macros: The macro detection and plotting functionality is inspired by the work of Lux Algo , particularly their widely-used indicators covering ICT concepts. 🎯 Core Features * **ICT Killzones:** Visualize critical trading sessions with customizable boxes. You can easily toggle and style the **Asia**, **London**, and **New York (AM, Lunch, PM)** sessions to focus on the liquidity and volatility that matter most to your strategy. * Fully customizable session times and colors. * Timezone support to align sessions with your local or preferred trading time (defaults to `America/New_York`). * **ICT Macros:** Automatically identify and plot specific, short-duration time windows where institutional algorithms are known to be active (e.g., `09:50-10:10`, `14:50-15:10`, etc.). * Plots the high/low range of the macro, providing clear levels of interest. * Utilizes 1-minute data for precision, even when viewing on 3-minute or 5-minute charts. 📚 Optimization over the other original indicators We add the custom input for macros session, users just need to input the from/to hour: minute format, and they will be converted into session objects in pinescript The macro draws function is optimized, removing redundant draws, leading to better performance Add "Distance from Macro Line to Chart" option Add "Session Drawings Limit" for better performance ⚠️ Notes on TradingView Warnings You may encounter some warnings from TradingView when using this script. These are generally expected due to the script's advanced, event-driven nature: 1. **Function Call Consistency:** The function 'box.new' should be called on each calculation for consistency, which may appear. This happens because drawing elements (like session boxes) are intentionally created only on the *first bar* of a new session, not on every single bar. This is a necessary design choice for performance and to prevent duplicate drawings. 2. **Potential for Repainting/Slow Load:** The **Macro** feature uses the `request.security_lower_tf()` function to get accurate 1-minute data. This can trigger warnings about performance or slow loading times. This is a known trade-off for achieving the precision required for the feature.
Penunjuk Pine Script®
oleh GTrader_indicators
6
Curious Buy - Sell Indicator - Institutional Zones (Smart Money)How the Script Works: 1. The Scripts identifies Institutional Demand , Supply & Neutral Zones with FIBS on the scripts with Rectangle BOX with labels in advance. User can insert desired start and end value to plot institutional zones 2. Script generates BUY - SELL signals shape based on candle stick formation in live market and labels with BUY - SELL image for easy identification 3. Script gives pop message EXIT SHORT once Buy spotted and candle close above the buy signal and same way EXIT LONG once Sell spotted and candle close below the buy signal 4. Scripts identifies the candle closing above the BUY - SELL signals Eg - If buy spotted the candle closing above the BUY signal with display with BLUE color Candle same way for sell signal the candle closing below the sell signal candle with display with BLACK color candle. 5. Script spots fake signals which are not valid and can be ignored by the end user 6. Three EMA's 20,50,200 has implemented to identify the strength of the market 7. Scripts identifies OPEN = LOW & OPEN = HIGH candle stick to spot the Institutional BUY - SELL activity 8. The script provides visual clues on the chart to help users identify potential trading opportunities. 9. The script provides visual clues on the chart to help users identity potential trading opportunities in live market 10. The looks and parameters of the script can be modified by end user to customize and adapt to different strategy. 11. With the script user can check higher time frame DAILY \ WEEKLY BUY - SELL signals to plan intraday trades and plan safe BUY - SELL positions. How Users Can Make Profit Using This Script: 1. Identify potential BUY - LONG opportunities: When a valid BUY is detected and condition is met, it is suggested to opening BUY position with stoploss below the BUY signal spotted candle. Safe users can execute BUY position once BLUE COLOR candle is formed, Wait for pull back to reduce the stoploss 2. Identify potential SELL - SHORT opportunities: When a valid SELL is detected and condition is met, it suggests a potential opening SELL positions with stoploss above the BUY signal spotted candle. Safe users can execute SELL position once BLACK COLOR candle is formed, Wait for pull back to reduce the stoploss. 3. Script generated BUY - SELL signal met target with the Institutional zone. Eg if BUY spotted at demand zone target will be neutral zone & Supply zone. 4. Script designed for user to spot high probability trades when BUY SIGNAL SPOTTED at the Institutional Demand zone same way SELL SIGNAL SPOTTED AT INSTITUTIONAL supply zone. 5. Combine with additional analysis: Users can utilize this script as a tool in their overall trading strategy. They can combine the signals with fundament analysis , market sentiment to make more informed trading decision 6.Set risk management measures: It is important for users to implement proper risk management strategies when trading based on the scripts signals. To avoid potential losses user once spotted BUY - SELL execute the long or short position. Ensure to place the stoploss to avoid potential losses and place the target. Once your trade is moving in your favor can trial your stoploss to cost and protect the profits.
Penunjuk Pine Script®
oleh curioustraderr
17
Higher-timeframe requests█   OVERVIEW This publication focuses on enhancing awareness of the best practices for accessing higher-timeframe (HTF) data via the request.security() function. Some "traditional" approaches, such as what we explored in our previous `security()` revisited publication, have shown limitations in their ability to retrieve non-repainting HTF data. The fundamental technique outlined in this script is currently the most effective in preventing repainting when requesting data from a higher timeframe. For detailed information about why it works, see this section in the Pine Script™ User Manual . █   CONCEPTS Understanding repainting Repainting is a behavior that occurs when a script's calculations or outputs behave differently after restarting it. There are several types of repainting behavior, not all of which are inherently useless or misleading. The most prevalent form of repainting occurs when a script's calculations or outputs exhibit different behaviors on historical and realtime bars. When a script calculates across historical data, it only needs to execute once per bar, as those values are confirmed and not subject to change. After each historical execution, the script commits the states of its calculations for later access. On a realtime, unconfirmed bar, values are fluid . They are subject to change on each new tick from the data provider until the bar closes. A script's code can execute on each tick in a realtime bar, meaning its calculations and outputs are subject to realtime fluctuations, just like the underlying data it uses. Each time a script executes on an unconfirmed bar, it first reverts applicable values to their last committed states, a process referred to as rollback . It only commits the new values from a realtime bar after the bar closes. See the User Manual's Execution model page to learn more. In essence, a script can repaint when it calculates on realtime bars due to fluctuations before a bar's confirmation, which it cannot reproduce on historical data. A common strategy to avoid repainting when necessary involves forcing only confirmed values on realtime bars, which remain unchanged until each bar's conclusion. Repainting in higher-timeframe (HTF) requests When working with a script that retrieves data from higher timeframes with request.security() , it's crucial to understand the differences in how such requests behave on historical and realtime bars . The request.security() function executes all code required by its `expression` argument using data from the specified context (symbol, timeframe, or modifiers) rather than on the chart's data. As when executing code in the chart's context, request.security() only returns new historical values when a bar closes in the requested context. However, the values it returns on realtime HTF bars can also update before confirmation, akin to the rollback and recalculation process that scripts perform in the chart's context on the open bar. Similar to how scripts operate in the chart's context, request.security() only confirms new values after a realtime bar closes in its specified context. Once a script's execution cycle restarts, what were previously realtime bars become historical bars, meaning the request.security() call will only return confirmed values from the HTF on those bars. Therefore, if the requested data fluctuates across an open HTF bar, the script will repaint those values after it restarts. This behavior is not a bug; it's simply the default behavior of request.security() . In some cases, having the latest information from an unconfirmed HTF bar is precisely what a script needs. However, in many other cases, traders will require confirmed, stable values that do not fluctuate across an open HTF bar. Below, we explain the most reliable approach to achieve such a result. Achieving consistent timing on all bars One can retrieve non-fluctuating values with consistent timing across historical and realtime feeds by exclusively using request.security() to fetch the data from confirmed HTF bars. The best way to achieve this result is offsetting the `expression` argument by at least one bar (e.g., `close [1 ]`) and using barmerge.lookahead_on as the `lookahead` argument. We discourage the use of barmerge.lookahead_on alone since it prompts the function to look toward future values of HTF bars across historical data, which is heavily misleading. However, when paired with a requested `expression` that includes a one-bar historical offset, the "future" data the function retrieves is not from the future. Instead, it represents the last confirmed bar's values at the start of each HTF bar, thus preventing the results on realtime bars from fluctuating before confirmation from the timeframe. For example, this line of code uses a request.security() call with barmerge.lookahead_on to request the close price from the "1D" timeframe, offset by one bar with the history-referencing operator [ ] . This line will return the daily price with consistent timing across all bars: float htfClose = request.security(syminfo.tickerid, "1D", close , lookahead = barmerge.lookahead_on) Note that:  • This technique only works as intended for higher-timeframe requests .  • When designing a script to work specifically with HTFs, we recommend including conditions to prevent request.security() from accessing timeframes equal to or lower than the chart's timeframe, especially if you intend to publish it. In this script, we included an if structure that raises a runtime error when the requested timeframe is too small.  • A necessary trade-off with this approach is that the script must wait for an HTF bar's confirmation to retrieve new data on realtime bars, thus delaying its availability until the open of the subsequent HTF bar. The time elapsed during such a delay varies with each market, but it's typically relatively small. 👉 Failing to offset the function's `expression` argument while using barmerge.lookahead_on will produce historical results with lookahead bias , as it will look to the future states of historical HTF bars, retrieving values before the times at which they're available in the feed. See the `lookahead` and Future leak with `request.security()` sections in the Pine Script™ User Manual for more information. Evolving practices The fundamental technique outlined in this publication is currently the only reliable approach to requesting non-repainting HTF data with request.security() . It is the superior approach because it avoids the pitfalls of other methods, such as the one introduced in the `security()` revisited publication. That publication proposed using a custom `f_security()` function, which applied offsets to the `expression` and the requested result based on historical and realtime bar states. At that time, we explored techniques that didn't carry the risk of lookahead bias if misused (i.e., removing the historical offset on the `expression` while using lookahead), as requests that look ahead to the future on historical bars exhibit dangerously misleading behavior. Despite these efforts, we've unfortunately found that the bar state method employed by `f_security()` can produce inaccurate results with inconsistent timing in some scenarios, undermining its credibility as a universal non-repainting technique. As such, we've deprecated that approach, and the Pine Script™ User Manual no longer recommends it. █   METHOD VARIANTS In this script, all non-repainting requests employ the same underlying technique to avoid repainting. However, we've applied variants to cater to specific use cases, as outlined below: Variant 1 Variant 1, which the script displays using a lime plot, demonstrates a non-repainting HTF request in its simplest form, aligning with the concept explained in the "Achieving consistent timing" section above. It uses barmerge.lookahead_on and offsets the `expression` argument in request.security() by one bar to retrieve the value from the last confirmed HTF bar. For detailed information about why this works, see the Avoiding Repainting section of the User Manual's Other timeframes and data page. Variant 2 Variant 2 ( fuchsia ) introduces a custom function, `htfSecurity()`, which wraps the request.security() function to facilitate convenient repainting control. By specifying a value for its `repaint` parameter, users can determine whether to allow repainting HTF data. When the `repaint` value is `false`, the function applies lookahead and a one-bar offset to request the last confirmed value from the specified `timeframe`. When the value is `true`, the function requests the `expression` using the default behavior of request.security() , meaning the results can fluctuate across chart bars within realtime HTF bars and repaint when the script restarts. Note that:  • This function exclusively handles HTF requests. If the requested timeframe is not higher than the chart's, it will raise a runtime error .  • We prefer this approach since it provides optional repainting control. Sometimes, a script's calculations need to respond immediately to realtime HTF changes, which `repaint = true` allows. In other cases, such as when issuing alerts, triggering strategy commands, and more, one will typically need stable values that do not repaint, in which case `repaint = false` will produce the desired behavior. Variant 3 Variant 3 ( white ) builds upon the same fundamental non-repainting approach used by the first two. The difference in this variant is that it applies repainting control to tuples , which one cannot pass as the `expression` argument in our `htfSecurity()` function. Tuples are handy for consolidating `request.*()` calls when a script requires several values from the same context, as one can request a single tuple from the context rather than executing multiple separate request.security() calls. This variant applies the internal logic of our `htfSecurity()` function in the script's global scope to request a tuple containing open and `srcInput` values from a higher timeframe with repainting control. Historically, Pine Script™ did not allow the history-referencing operator [ ] when requesting tuples unless the tuple came from a function call, which limited this technique. However, updates to Pine over time have lifted this restriction, allowing us to pass tuples with historical offsets directly as the `expression` in request.security() . By offsetting all items in a tuple `expression` by one bar and using barmerge.lookahead_on , we effectively retrieve a tuple of stable, non-repainting HTF values. Since we cannot encapsulate this method within the `htfSecurity()` function and must execute the calculations in the global scope, the script's "Repainting" input directly controls the global `offset` and `lookahead` values to ensure it behaves as intended. Variant 4 (Control) Variant 4, which the script displays as a translucent orange plot, uses a default request.security() call, providing a reference point to compare the difference between a repainting request and the non-repainting variants outlined above. Whenever the script restarts its execution cycle, realtime bars become historical bars, and the request.security() call here will repaint the results on those bars. █   Inputs Repainting The "Repainting" input (`repaintInput` variable) controls whether Variant 2 and Variant 3 are allowed to use fluctuating values from an unconfirmed HTF bar. If its value is `false` (default), these requests will only retrieve stable values from the last confirmed HTF bar. Source The "Source" input (`srcInput` variable) determines the series the script will use in the `expression` for all HTF data requests. Its default value is close . HTF Selection This script features two ways to specify the higher timeframe for all its data requests, which users can control with the "HTF Selection" input (`tfTypeInput` variable):  1) If its value is "Fixed TF", the script uses the timeframe value specified by the "Fixed Higher Timeframe" input (`fixedTfInput` variable). The script will raise a runtime error if the selected timeframe is not larger than the chart's.  2) If the input's value is "Multiple of chart TF", the script multiplies the value of the "Timeframe Multiple" input (`tfMultInput` variable) by the chart's timeframe.in_seconds() value, then converts the result to a valid timeframe string via timeframe.from_seconds() . Timeframe Display This script features the option to display an "information box", i.e., a single-cell table that shows the higher timeframe the script is currently using. Users can toggle the display and determine the table's size, location, and color scheme via the inputs in the "Timeframe Display" group. █   Outputs This script produces the following outputs:  • It plots the results from all four of the above variants for visual comparison.  • It highlights the chart's background gray whenever a new bar starts on the higher timeframe, signifying when confirmations occur in the requested context.  • To demarcate which bars the script considers historical or realtime bars, it plots squares with contrasting colors corresponding to bar states at the bottom of the chart pane.  • It displays the higher timeframe string in a single-cell table with a user-specified size, location, and color scheme. Look first. Then leap.
Penunjuk Pine Script®
oleh PineCoders
14
40+ Coin Screener (workaround to 40 Security Limit Per Script) This is a far inferior method for a screener/scanner (compared to my first publication) but after looking at that script from a noobs eyes again, I could see how this form would be a lot easier to take in/understand so wanted to publish it. Everything that I could think of to mention about this is in my 1st pub so ill leave it to you to check it out...though I did include some comments in the script. It is pretty straight forward but if you have any questions don't hold them in. I'll answer them if I can. The only thing that is not in this one is setting up the alert feature so that you only have to create 1 alert per iteration of the script and it takes care of all of the coins for that iteration/set that is chosen in the settings (so please see previous script if would like to do this for your screener/scanner). To be PERFECTLY CLEAR, the workaround is to the issue of not being able to scan but only 40 coins per script. You can scan more than 40 per script but only if you create "batches" or "sets" that the user can select within the settings which set to use for each iteration of the script on the chart. That being, you have to the script multiple times to the chart and merge them into 1 window and merge the scales (instructions in first publications). Here in this script I am scanning 72 different coins that are the Margin Coins on KUCOIN. I have split them up into 3 sets (24 coins per set). I could have made 2 sets but the script will be slower to load and to respond (like, when it comes to receiving alerts), thus I split them up the way I did. If you want to change any of this there are slightly more details in the previous script. One great use-case that I LOVE about this particular version (and the way I use it) is right at the end of when I see a whole market dump/pump coming to an end and want to know which horse to bet on. Used to think whichever coin come out the fastest from the dump was the one to bet on but quickly learned that 1-2 (or even a few) hrs needs to go by first bc the ones that look the strongest in the beginning are NOT the ones to have performed the best when viewing the results 12 hrs later. IN FACT, many instances of using this exact script for reasons as such has taught me that the manipulators (I believe this to be the case as least) WANT everyone to bet on these that come out the gate the hardest and thus they make them move REALLY hard in the beginning then they QUICKLY become stagnant (moreso, they become WORSE than stagnant, they actually quickly retrace to put you into the negative so that you get out to get into the others now moving (to provide the market with more liquidity. They WANT you to get into a coin thats moving crazy hard so that they can then cease that movement once many fall for the trick just to then make that once strong looking coin now stagnant and make others move crazy hard. They wait for you to get out of the 1st and into the next set of movers just to do this time and time again bc hey, what are we sheep good for other than to provide the big guns with liquidity, am I right? Thats rhetorical, which you would know if you've ever had this happen to you (without a doubt MANY of you have). Let this script (above all other things) provide good evidence to back up this cynical way of viewing the markets to anyone that is questioning it. This prolonged time between when the dump is over and when the ACTUAL movers REALLY start moving can actually be of great benefit to us sheep if used correctly, Firstly, it gives us some time to determine if when we thought was the bottom, ACTUALLY was the bottom. That bottom is easily determined if there are no (or very few) coins that went any lower than the point in time that the script began calculating on. Secondly, it allows us time to wait for the REAL movers and shakers to start moving and shaking. One new feature that I LOVE that TV has implemented is the ability (once the script is added to the chart) to be able to click a point in time on the chart where you want the script to begin its calculations. If this point needs to be changed at any point in time then you can either go into the setting and input the time you wish or simply remove the script and add it again so that you are prompted to select another point in time. Ok, I think that everything I wanted to say. The next version that I will add will be probably my favorite and most used by yours truly...not to mention unique in a way that I have yet to see an implementation anything like it in all of TV's public library. Not to say its not there, but I have yet to come across it and I have DEFINITELY done my fair share of searching for it when I couldn't figure out how to code it for the longest time (though, I was and still am a noob so might get some great feedback on better ways to approach it, but we'll save that jabbering for the next of the publications. I hope each and every one of ya'll (yes, Im from the South) have the GREATEST of Thanksgivings (if in the US that is...I graced my parents with the best gift anyone could have given them 35 years ago on Thanksgiving....MEEEE ;) So I will sure as hell be having a great holiday. Thanks for checking out my script...you can "like" and leave a comment if you so feel the urge to...or not. Im not doing this for me, but rather to stretch my arms out as far as possible to benefit the most people as possible and more people would see the script if it has more likes/comments/traffic pointing towards it...not to mention as other publishers have...it IS gratifying to see a few likes in my side window, which btw, I have MANY more variations and completely diff types of scanners/screeners Ill be publishing in the future and to know that they've become of use....I"VE become of use to the community is very....pleasing to me and does (as I've also seen many publishers mention as well) drive me to want to publish ones that I originally thought I would keep for myself. Peace out people.
Penunjuk Pine Script®
oleh A_Traders_Edge
38
Pinescript - Common String Functions Library by RRBCommon String Functions Library by RagingRocketBull 2021 Version 1.0 Pinescript now has strong support for arrays with many powerful functions, but still lacks built-in string functions. Luckily you can easily process and manipulate strings using arrays. This script provides a library of common string functions for everyday use, such as: indexOf, substr, replace, ascii_code, str_to_int etc. There are 100+ unique functions (130 including all implementations) It should serve as building blocks to speed up the development of your custom scripts. You should also be able to learn how Pinescript arrays works and how you can process strings. Similar libraries for Array and Statistical Functions are in the works. You can find the full list of functions below. Features: - 100+ unique string functions (130 including all implementations) in categories: lookup, testing, conversion, modification, extraction, type conversion, date and time, console output - Live Output for all/selected functions based on User Input. Test any function before using in script. - Live Unit Test Output for several functions based on pre-defined inputs. - Output filters: show unique functions/all implementations, grouping - Console customization options: set custom text size, color, page length - Support for Pages - auto splits output into pages with fixed length, use pages in your scripts - Several easy to use console output functions to speed up debugging/output. WARNING: - Compilation Time: 1 min Notes: - uses Pinescript v3 Compatibility Framework - this script is packed to the max and sets a new record in testing of Pinescript's limits: 500 local scopes, 4000+ lines, 180kb+ source size. It's not possible to add more ifs/fors/functions without reducing functionality - to fit the max limit of local scopes = 500 all ifs were replaced with ?: where possible, the number of function calls was reduced, some calls replaced with inline function code - ifs are faster (especially when lots of them are used in a for cycle), more readable, but ifs/fors/functions increase local scopes (+1) and compiled file size, have max nesting limit = 10. - ?: are slower (especially in for cycles), hard to read when nested, don't affect local scopes, reduce compiled file size, can't contain plots, for statements (break/continue) and sets of statements - for most array functions to work (except push), an array must be defined with at least 1 pre-existing dummy element 0. - if you see "String too long" error - enable Show Pages, reduce Max Chars Per Page < Max String Length limit = 4096. - if you see "Loop too long" error - hide/unhide or reattach the script - some functions have several implementations that can be faster/slower, use internal code/ext functions - 1 is manual string processing using for cycles (array.get) and ext functions - provided in case you want to implement your own logic, may sometimes be slower - 2 is a 2nd alternate implementation mostly done using built-in functions (array.indexof, array.slice, array.insert, array.remove, str.replace_all), attempts to minimize local scopes and dependency on ext functions, should generally be faster - 3 is a 3rd alternate (array.includes, array.fill) or a more advanced implementation (datetime3_str) with lots of params, giving you the most control over output - most functions have dependencies, such as const names, global arrays, inputs, other functions. P.S. Strings of Time may be closed unto themselves or have loose ends; they can vibrate, stretch, join or split. Function Groups: 1. Char Functions - repeat(str, num) - ascii_char(code) - ascii_code(char) - is_digit(char) - is_letter(char) - digit_to_int(char) - is_space_char(char) 2. Char Test and Lookup Functions - char_at(str, pos) - char_code_at(str, pos) - indexOf_char(str, char) - lastIndexOf_char(str, char) - nth_indexOf_char(str, char, num) - includes_char(str, char) 3. String Lookup Functions - indexOf(str, target) - lastIndexOf(str, target) - nth_indexOf(str, target, num) - indexesOf(str, target) - numIndexesOf(str, target) 4. String Conversion Functions - lowercase(str) - uppercase(str) 5. String Modification and Extraction Functions - split(str, separator) - insert(str, pos, new_str) - remove(str, pos, length) - insert_char(str, pos, char) - remove_char(str, pos) - reverse(str) - fill_char(str, char, start_pos, end_pos) - replace(str, target, new_str) - replace_first(str, target, new_str) - replace_last(str, target, new_str) - replace_nth(str, target, new_str, num) - replace_left(str, new_str) - replace_right(str, new_str) - replace_middle(str, pos, new_str) - left(str, num) - right(str, num) - first_char(str) - last_char(str) - truncate(str, max_len) - truncate_middle2(str, trunc_str, pos, max_len) - truncate_from2(str, trunc_str, pos, max_len, side) - concat(str1, str2, trunc_str, max_len, mode) - concat_from(str1, str2, trunc_str, max_len, side, mode) - trim(str) - substr(str, pos, length) - substring(str, start_pos, end_pos) - strip(str, mask, target, is_allowed) - extract_groups(str) - extract_numbers(str, d1, d2, mode) - str_to_float(str, d1, d2) - str_to_int(str) - extract_ranges(str, d1, d2, d3, type) 6. String Test Functions - includes(str, target) - starts_with(str, target) - ends_with(str, target) - str_compare(str1, str2) 7. Type Conversion Functions - tf_check2(tf) - tf_to_mins() - convert_tf(tf) - period_to_mins(tf) - convert_tf2(tf) - convert_tf3(tf) - bool_to_str(flag) - get_src(src_str) - get_size(size_str) - get_style(style) - get_bool(bool_str) - get_int(str) - get_float(str, d1, d2) - get_color(str, def_color) - color_tr2(col_str, transp) - get_month(str) - month_name(num, format) - weekday_name(num, format) - dayofweek_name(t) 8. Date and Time Functions - date_str(t, d) - time_str(t, d) - datetime_str(t, d1, d2) - date2_str(t, d, type) - time2_str(t, d, type) - datetime2_str(t, d1, d2, format1, format2) - date3_str(t, template) - time3_str(t, template) - datetime3_str(t, template) 9. Console Output & Helper Functions - echo1(con, str) - echo2(x, y, con, str) - echo3(v_shift, con, str, msg_color, text_size) - echo4(x, y, con, str, msg_style, msg_color, text_size, text_align, msg_xloc) - echo5(x, y, con, str, msg_style, msg_color, text_size, text_align, msg_xloc) - echo6(x, y, con, str) - echo7(v_shift, con, str, msg_color, text_size) - echo8(x, y, con, str, msg_style, msg_color, text_size, text_align, msg_xloc) - echo9(x, y, con, str, msg_style, msg_color, text_size, text_align, msg_xloc) - new_page(str, line_str, trunc_str, header_str, footer_str, length, page_count, page, mode)
Penunjuk Pine Script®
oleh RagingRocketBull
17
[blackcat] L2 Zero-lag EMA Swing TradeLevel: 2 Background This script is a comprehensive work of mine, incorporating Ehlers zero-lag EMA and my first script published: MA fingerprint for long entries. Function Ehlers zero-lag EMA algorithm in this scripts is mainly used for short signal production, while my MA fingerprint algorithm is used for long entries. Key Signal a ---> Ehlers Zero-lag EMA fast line for subjective long jugement b ---> Ehlers Zero-lag EMA slow line for subjective short jugement long --> Swing long entry with partial postion short --> Swing short entry with partial postion Remarks Feedbacks are appreciated. This script is optimized for 1D time frame. Readme In real life, I am a prolific inventor. I have successfully applied for more than 60 international and regional patents in the past 12 years. But in the past two years or so, I have tried to transfer my creativity to the development of trading strategies. Tradingview is the ideal platform for me. I am selecting and contributing some of the hundreds of scripts to publish in Tradingview community. Welcome everyone to interact with me to discuss these interesting pine scripts. The scripts posted are categorized into 5 levels according to my efforts or manhours put into these works. Level 1 : interesting script snippets or distinctive improvement from classic indicators or strategy. Level 1 scripts can usually appear in more complex indicators as a function module or element. Level 2 : composite indicator/strategy. By selecting or combining several independent or dependent functions or sub indicators in proper way, the composite script exhibits a resonance phenomenon which can filter out noise or fake trading signal to enhance trading confidence level. Level 3 : comprehensive indicator/strategy. They are simple trading systems based on my strategies. They are commonly containing several or all of entry signal, close signal, stop loss, take profit, re-entry, risk management, and position sizing techniques. Even some interesting fundamental and mass psychological aspects are incorporated. Level 4 : script snippets or functions that do not disclose source code. Interesting element that can reveal market laws and work as raw material for indicators and strategies. If you find Level 1~2 scripts are helpful, Level 4 is a private version that took me far more efforts to develop. Level 5 : indicator/strategy that do not disclose source code. private version of Level 3 script with my accumulated script processing skills or a large number of custom functions. I had a private function library built in past two years. Level 5 scripts use many of them to achieve private trading strategy.
Penunjuk Pine Script®
oleh blackcat1402
6
HTF Oscillators RSI/ROC/MFI/CCI/AO - Dynamic SmoothingThe Interplay of Time Frames: A Balanced View Navigating the markets often involves interpreting trends from multiple angles. The HTF Oscillators with Dynamic Smoothing indicator enables you to do just that. This tool provides the option to integrate smoothed oscillator readings from Higher Time Frames (HTF) into lower time frame charts, such as a 1-minute chart. By doing so, the indicator offers a balanced viewpoint that bridges the gap between micro and macro perspectives, helping you make informed decisions without losing sight of the broader market context. Features Multi-Oscillator Support Choose from a range of popular oscillators like the Relative Strength Index (RSI), Rate of Change (ROC), Money Flow Index (MFI), Commodity Channel Index (CCI), and Awesome Oscillator (AO). These oscillators are commonly used as foundational building blocks in trading strategy scripts by traders worldwide. Switch effortlessly between them, depending on your trading strategy and requirements. To maintain consistency and a familiar user experience, our script adopts the same visual aesthetics that you'll find in Pine Script indicators on TradingView: a sleek purple line for the oscillator and a transparent band filling. These visual elements are not only pleasing to the eye but also widely appreciated by the trading community. Dynamic Smoothing The unique dynamic smoothing feature calculates a smoothing factor based on the ratio of minutes between the Higher Time Frame (HTF) and your current time frame. This provides a sleek and responsive oscillator line that still holds the weight of the longer trend. One of the significant advantages of this feature is user experience; when you change your time frame, the HTF-values in your settings will remain consistent. This ensures that you can easily switch between different time frames without losing the insights provided by your selected HTF. Visual Aids Visual cues are an essential part of any trading strategy. The indicator not only plots signals to mark overbought and oversold conditions based on the dynamically smoothed oscillator but also provides you with the flexibility to customize your visual experience. You have the option to toggle on/off the display of these signals depending on your specific needs. Additionally, bands can be displayed at overbought and oversold levels, along with a reference middle line. If you switch between different oscillators (available in the parameter settings), remember to manually adjust the bands in the input settings to ensure signals matches with the type of oscillator to your liking. User-Friendly Settings We've grouped related settings together, making it easier for you to find what you're looking for. Adjust the oscillator type, length of bars, smoothing settings, and more with just a few clicks. Information Table A standout feature of this indicator is the real-time information table, which displays the values of all selected oscillators based on your specified Higher Time Frame (HTF) settings. This can be particularly useful for traders who depend on multiple indicators for their decision-making process. The data presented in the table is synchronized with the HTF options you've configured in the input settings, allowing for a more efficient and quick scan of values from higher time frames. Educational Corner: The Power of the Information Table and Customization The table incorporated into this indicator isn't just eye-candy; it's a practical tool designed to elevate your trading strategy. It dynamically displays real-time values of various oscillators for the HTF you've chosen. This is an exemplary use of TradingView's scripting capabilities to blend multiple indicators into a single visual panel, streamlining your analysis and decision-making process. But here's the best part: You're not limited to what we've created. With some basic understanding of TradingView's scripting language, Pine Script, you can easily adapt this table to include different indicators that suit your unique trading style. The logic in the script is modular and can serve as a foundation for your own customized trading dashboard. So, go ahead, get creative and explore new combinations of indicators that will help you excel in your trading endeavors! You no longer have to toggle between different charts or indicators to get the information you need; it's all there in one neatly organized table. We encourage you to tap into this feature and make it your own, empowering your trading like never before. By doing so, you not only gain a more comprehensive toolset, but you also engage more deeply with your trading strategy, understanding its nuances and, ultimately, making more informed decisions. Conclusion The HTF Oscillators with Dynamic Smoothing is a versatile and powerful tool that brings together the best of both worlds: the perspective of higher time frames and the granularity of shorter ones. Its feature-rich setting options and real-time information table make it a potential useful addition to your trading toolkit. Remember, while this indicator offers a comprehensive and smarter way to look at the markets, it is not a foolproof method for predicting market movements. Always use it in conjunction with other analysis methods and risk management strategies.
Penunjuk Pine Script®
oleh Harrocop
2
BT Leading Candle IndicatorThe oscillator display consists of 3 lines (K, D and J - hence the name of the display) and 2 levels. K and D are the same lines you see when using the stochastic oscillator. The J line in turn represents the deviation of the D value from the K value. The convergence of these lines indicates new trading opportunities. Just like the Stochastic Oscillator, oversold and overbought levels correspond to the times when the trend is likely to reverse. Function BT Leading KDJ Candle Indicator use candles to indicate KD relationship. E.g. yellow candles for bull (K>=D) and fuchsia candles for bear (K=D and fuchsia for K KDJ K value d --> KDJ D value buysig --> KD buy signal in green triangle selsig --> KD sell signal in red triangle leadingline --> colorful leading line for KDJ Pros and Cons Pros: 1. Candle height can indicates the strength of trend and different colors are used for indicating KD relationship 2. a leading line is added as aux method to confirm KDJ signal Cons: 1. It may satruate for extreme conditions of long and short as described in the chart, which is inherent KDJ shortcoming. 2. Not accurate for long and short entries and need filtering out noise and fake signal. Remarks More direct to observe and confirm trend with the leading line. Read me In real life, I am a prolific inventor. I have successfully applied for more than 60 international and regional patents in the past 12 years. But in the past two years or so, I have tried to transfer my creativity to the development of trading strategies. Trading view is the ideal platform for me. I am selecting and contributing some of the hundreds of scripts to publish in Trading view community. Welcome everyone to interact with me to discuss these interesting pine scripts. The scripts posted are categorized into 5 levels according to my efforts or man hours put into these works. Level 1 : interesting script snippets or distinctive improvement from classic indicators or strategy. Level 1 scripts can usually appear in more complex indicators as a function module or element. Level 2 : composite indicator/strategy. By selecting or combining several independent or dependent functions or sub indicators in proper way, the composite script exhibits a resonance phenomenon which can filter out noise or fake trading signal to enhance trading confidence level. Level 3 : comprehensive indicator/strategy. They are simple trading systems based on my strategies. They are commonly containing several or all of entry signal, close signal, stop loss, take profit, re-entry, risk management, and position sizing techniques. Even some interesting fundamental and mass psychological aspects are incorporated. Level 4 : script snippets or functions that do not disclose source code. Interesting element that can reveal market laws and work as raw material for indicators and strategies. If you find Level 1~2 scripts are helpful, Level 4 is a private version that took me far more efforts to develop. Level 5 : indicator/strategy that do not disclose source code. private version of Level 3 script with my accumulated script processing skills or a large number of custom functions. I had a private function library built in past two years. Level 5 scripts use many
Penunjuk Pine Script®
oleh Baiju89
6
[blackcat] L1 Jon Andersen R-Squared IndicatorLevel: 1 Background The R-Squared indicator created by Jon Andersen in "Standard error bands" in the September 1996 STOCKS & COMMODITIES . Function This script fristly creates the coeffR function which is used to produced the R-Squared indicator. The coeffR function is used to calculate the correlation coefficient R. Once I have created and verified the coeffR function, the R-Sqaured indicator can be built easily. Key Signal AvgSqrR --> Smoothed R-Squared Oscillator Output. Labels and alerts are added. Remarks Feedbacks are appreciated. Readme In real life, I am a prolific inventor. I have successfully applied for more than 60 international and regional patents in the past 12 years. But in the past two years or so, I have tried to transfer my creativity to the development of trading strategies. Tradingview is the ideal platform for me. I am selecting and contributing some of the hundreds of scripts to publish in Tradingview community. Welcome everyone to interact with me to discuss these interesting pine scripts. The scripts posted are categorized into 5 levels according to my efforts or manhours put into these works. Level 1 : interesting script snippets or distinctive improvement from classic indicators or strategy. Level 1 scripts can usually appear in more complex indicators as a function module or element. Level 2 : composite indicator/strategy. By selecting or combining several independent or dependent functions or sub indicators in proper way, the composite script exhibits a resonance phenomenon which can filter out noise or fake trading signal to enhance trading confidence level. Level 3 : comprehensive indicator/strategy. They are simple trading systems based on my strategies. They are commonly containing several or all of entry signal, close signal, stop loss, take profit, re-entry, risk management, and position sizing techniques. Even some interesting fundamental and mass psychological aspects are incorporated. Level 4 : script snippets or functions that do not disclose source code. Interesting element that can reveal market laws and work as raw material for indicators and strategies. If you find Level 1~2 scripts are helpful, Level 4 is a private version that took me far more efforts to develop. Level 5 : indicator/strategy that do not disclose source code. private version of Level 3 script with my accumulated script processing skills or a large number of custom functions. I had a private function library built in past two years. Level 5 scripts use many of them to achieve private trading strategy.
Penunjuk Pine Script®
oleh blackcat1402
[blackcat] L1 Jon Andersen Standard Error BandsLevel: 1 Background The standard error bands created by Jon Andersen in "Standard error bands" in the September 1996 STOCKS & COMMODITIES. Function This script calculates the beta and alpha coefficients of the linear regression. First, it creates the calcB and calcA functions, which refer to the beta and alpha coefficients. Create calcB first, then calcA. These functions are used in calculating the regression coefficients for the standard error bands. In This standard error bands indicator, the "Length" value specifies the period of the linear regression line; the default is 21. The SDeg value specifies the smoothing factor that is used to smooth the linear regression and standard error bands; the default is 3. Key Signal LinRegS --> standard error bands center line LinRegS + SErr --> standard error bands upper line LinRegS - SErr --> standard error bands lower line Labels and alerts are added. Remarks Feedbacks are appreciated. Readme In real life, I am a prolific inventor. I have successfully applied for more than 60 international and regional patents in the past 12 years. But in the past two years or so, I have tried to transfer my creativity to the development of trading strategies. Tradingview is the ideal platform for me. I am selecting and contributing some of the hundreds of scripts to publish in Tradingview community. Welcome everyone to interact with me to discuss these interesting pine scripts. The scripts posted are categorized into 5 levels according to my efforts or manhours put into these works. Level 1 : interesting script snippets or distinctive improvement from classic indicators or strategy. Level 1 scripts can usually appear in more complex indicators as a function module or element. Level 2 : composite indicator/strategy. By selecting or combining several independent or dependent functions or sub indicators in proper way, the composite script exhibits a resonance phenomenon which can filter out noise or fake trading signal to enhance trading confidence level. Level 3 : comprehensive indicator/strategy. They are simple trading systems based on my strategies. They are commonly containing several or all of entry signal, close signal, stop loss, take profit, re-entry, risk management, and position sizing techniques. Even some interesting fundamental and mass psychological aspects are incorporated. Level 4 : script snippets or functions that do not disclose source code. Interesting element that can reveal market laws and work as raw material for indicators and strategies. If you find Level 1~2 scripts are helpful, Level 4 is a private version that took me far more efforts to develop. Level 5 : indicator/strategy that do not disclose source code. private version of Level 3 script with my accumulated script processing skills or a large number of custom functions. I had a private function library built in past two years. Level 5 scripts use many of them to achieve private trading strategy.
Penunjuk Pine Script®
oleh blackcat1402
7